Autoprefixer not working about clutch

[joseBasso]

From next docs - "Warning: When you define a custom PostCSS configuration file, Next.js completely disables the default behavior" (auto prefixer and etc.).

Looks like we need to add the default postcss stuff to our custom config

Next.js Customizing PostCSS plugins

[joseBasso]

Fixed the problem on Minimal Template so any future projects won't hit this problem. If we feel the need to migrate old projects, let me know and I'll do it

[MatthewHager]

I think this is fine. We can manually update existing projects. However, I want to make sure that our config file is exactly like the defaults provided by Next. Would be awesome if there was a way to extend instead of override. If Next.js updates this file, would be great if that flowed through somehow. This was an easy issue to miss because it doesn't fail loudly.

[joseBasso]

True. CSS Nesting landed in Firefox a few weeks ago so if we are happy with the browser support - https://caniuse.com/css-nesting - we could remove the file and use the next.js default since our only override is postcss-nested.
However, this would mean that our sites don't run at all in IE and a few others

[joseBasso]

Never mind. CSS nesting in Chrome does not support nested rules that start with '&' so the approach of deleting the file won't work because our styles generation needs that

The solution in place solves everything except the scenario you wrote about Next.js updating the file. But from their docs it looks inevitable. On the bright side, it is unlikely and easy to solve if it happens so I don't think it is worth investing too much time into it.

We can revisit if you think it is important