Is postcss-cssnext still maintained?

No — postcss-cssnext stopped being maintained around May 2018. postcss-cssnext's own maintainers named postcss-preset-env as the successor.

• successor named by the maintainers
• high confidence
• package successor

What should I use instead of postcss-cssnext?

postcss-cssnext's own maintainers named postcss-preset-env as the successor. postcss-preset-env is not a drop-in replacement, so expect to change call sites.

How to migrate from postcss-cssnext to postcss-preset-env

Swap the plugin in your PostCSS config for postcss-preset-env and set stage plus a browserslist target. Autoprefixer is bundled, so remove any separate entry for it.

Why postcss-cssnext is on this list

The author deprecated postcss-cssnext on 29 May 2018 and named postcss-preset-env as its successor, which is now maintained under the PostCSS organisation. The repository was archived in December 2024 and the npm package carries the same deprecation notice. postcss-preset-env selects features from browserslist targets and standardisation stages rather than a fixed feature list.

The succession is settled: primary sources agree and the ecosystem has already moved.

postcss-cssnext alternatives

Beyond the primary recommendation, these are credible for postcss-cssnext's use case:

• autoprefixer — view on npm
• lightningcss — view on npm

Check your own project for postcss-cssnext

npx dead-deps --all --min-state unmaintained

Run that in the directory holding your lockfile. If postcss-cssnext is anywhere in your tree — a direct dependency or buried under something else — it appears in the report with this verdict, this successor and the same evidence links, alongside anything else that has stopped moving. Nothing is uploaded; the scan reads your lockfile locally and queries public registry metadata.

Exit code 1 means something was flagged, which makes npx dead-deps --min-state deprecated usable as a CI gate. See how verdicts are produced.

Evidence

Every claim on this page traces to a primary source. Check them:

• Author's post: Deprecating cssnext (29 May 2018)moox.io
• npm deprecation notice for postcss-cssnext ("deprecated in favor of postcss-preset-env")npmjs.com
• Archived MoOx/postcss-cssnext repositorygithub.com

Packages related to postcss-cssnext

• extract-text-webpack-pluginSuccessor named by the maintainers: mini-css-extract-plugin · unmaintained since…
• glamorousSuccessor named by the maintainers: @emotion/react · unmaintained since December 2018
• babel-preset-es2015Successor named by the maintainers: @babel/preset-env · unmaintained since April 2017
• create-react-appSuccessor named by the maintainers: vite · unmaintained since February 2025
• eslint-loaderSuccessor named by the maintainers: eslint-webpack-plugin · unmaintained since April 2020

See the full index of covered packages, or read the methodology for how a verdict is reached and why a quiet package is not a dead one.