Nuxt.js: Replace postcss-next with postcss-preset-env

[hauleth]

There is issue about deprecation of postcss-cssnext (MoOx/postcss-cssnext#445) in favour of postcss-preset-env which seems to be much more configureable and simpler in form of supporting new features.

_{This question is available on Nuxt.js community (#c7009)}

[MoOx]

I am the creator of cssnext and confirm that cssnext will be deprecated in a near future (nobody is really maintaining it - unlike preset-env)

[pi0]

Hey @MoOx. Thanks for the help and clarifying status :) We are going to release Nuxt 2.0 very soon. So do you recommend switching to preset-env right now?

[hauleth]

@pi0 as it would be breaking change (not everything that postcss-cssnext supports is available OOB in postcss-preset-env, to be exact preset-env OOB supports features only up to Stage 3 while cssnext supports at least Stage 1 (nesting rules)) I would vote for 2.0 version instead of current one.

[pi0]

@hauleth 1.x won't be affected :) Also nuxt 2 users can still optionally provide their postcssrc file to customize it's config.

[Extarys]

As long as there is a thorough migration guide so people don't spend a month trying to understand what they need to do to make it work I'm in.

[jhpratt]

postcss-cssnext was officially deprecated a few days ago in favor of postcss-preset-env.

[pi0]

Latest nuxt-edge and nuxt 2 will use postcss-preset-env by default.

@MoOx You made an amazing work with postcss-cssnext ❤️

I hope we can also provide an official CSS-In-JS solution in near future too :)

[cmty[bot]]

This feature-request has been implemented by @pi0 in release v2.0.0.

You can already try to use nuxt-edge :)

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.