postcss-nested VS autoprefixer

And we have to make sure that it runs before the nesting plugin, otherwise it will not work at all due to an issue when using both plugins together.

postcss-nested

What you're describing is nesting, which is currently in the proposal stages for CSS. That being said, nesting has long been a feature in many preprocessors, such as sass and less. You can also use this PostCSS plugin if you only want the nesting and nothing else.

My PostCSS Config contains postcss-preset-env already which should support for CSS nesting. I also installed postcss-nested & postcss-css-variables, just in case.

PostCSS Nested - so I can use Sass-like nesting.

A quick example that demonstrates what I've said would be the postcss nesting plugin: https://github.com/postcss/postcss-nested

Do you use Autoprefixer? https://github.com/postcss/autoprefixer

Simple, fast, and a little bit opinionated, Eleventy Plus Vite features Eleventy 2.0.0-canary, the new Eleventy 2.0 Dev Server with live reload, Vite 3.0 as Middleware in Eleventy Dev Server (using eleventy-plugin-vite), build output post-processing by Vite (with Rollup), CSS/Sass post-processing with PostCSS including Autoprefixer and cssnano, a custom CSS/Sass structure, basic fluid typography based on Utopia, dark mode support, an RSS feed, XML sitemap, and — to top it off — perfect scores on Lighthouse.

w/ postcss-preset-env(v7.8.3): convert modern CSS into something most browsers can understand, determining the polyfills you need based on your targeted browsers or runtime environments. It takes the support data that comes from MDN and Can I Use and determine from a browserlist whether those transformations are needed. It also packs Autoprefixer within and shares the list with it, so prefixes are only applied when you're going to need them given your browser support list.

As others have said, you need to normalize. Also, you may need something like autoprefixer if you're using styles that have different vendor prefixes. https://github.com/postcss/autoprefixer

Mmm maybe it's not gap then, maybe it's some other property. Maybe autoprefixer could help. Or polyfills, as other user suggested.

Of course, we have great tooling for that: Autoprefixer, PostCSS and Stylelint for CSS transformation, Babel and Webpack for JavaScript transpilation and bundling, ESLint for code analysis, and many others.

Bulma uses autoprefixer to make (most) Flexbox…