PostCSS 8 for end users

PostCSS 8 does not bring significant API changes for end-users. We dropped support for old Node.js versions, but API was not changed.

PostCSS 8 supports plugins from PostCSS 7. You just need to update postcss dependency and tool, which run postcss (like postcss-loader or postcss-cli). But some PostCSS runners didn’t publish a new version with PostCSS 8.

Webpack

✅ Supports PostCSS 8

1. Update postcss-loader to >= 4.0.2.
2. Add postcss dependency to your project or update it to >= 8.1.

CLI

✅ Supports PostCSS 8

1. Update postcss-cli to >= 8.0.
2. Add postcss dependency to your project.

JS API

✅ Supports PostCSS 8

1. Just update postcss dependency.
2. If you have custom plugins you may want to update them to avoid warning. See PostCSS 8.0 Migration Guide for Plugin Developers.

Gulp

✅ Supports PostCSS 8

1. Update gulp-postcss to >= 9.0.
2. Add postcss dependency to your project.

Create React App

❌ Support this PR to get PostCSS 8 in CRA 4.0.

For now, you need to avoid using PostCSS 8 plugins.

Gatsby

❌ Support this issue to update PostCSS 8 in Gatsby.

For now, you need to avoid using PostCSS 8 plugins.

Next.js

❌ Support this issue to update PostCSS 8 in Next.js.

For now, you need to avoid using PostCSS 8 plugins.

Nuxt.js

❌ Support this issue to get PostCSS 8 in Nuxt.js 2.0.

For now, you need to avoid using PostCSS 8 plugins.

Rollup

❌ Support this PR to update PostCSS 8 in Rollup.

For now, you need to avoid using PostCSS 8 plugins.

Parcel

❌ Support this PR to get PostCSS 8 in Parcel 2.0.

For now, you need to avoid using PostCSS 8 plugins.