Built-in CSS autoprefixing based on Browserslist config #5017
Replies: 3 comments 1 reply
-
In favor of this, also would be great to minify the code. I used to author my custom CSS in I also like the idea to support configurations for this, something like // remix.config.js
module.exports = {
css: {
minify: true,
autoprefix: true,
},
}; |
Beta Was this translation helpful? Give feedback.
-
The possibility to let Lightning CSS run on the generated css-bundle would be great! That would make it possible, for example, to use CSS Nesting syntax in CSS Modules. |
Beta Was this translation helpful? Give feedback.
-
This got discussed in Roadmap #5, around 38'46 and accepted. Tracked in #5315 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Right now, if you want to use Autoprefixer, you need to run a separate PostCSS step ahead of time which is a bit clunky. It would be nice if this was built-in using your project's Browserslist config via
.browserslistrc
or the"browserslist"
field inpackage.json
.Another nice benefit of being built-in is that we could choose to use alternative tools like Lightning CSS.
This would need to be opt-in so it's not a breaking change, but I can imagine this becoming the default behaviour in a future major release.
Related issues/RFCs/proposals
Beta Was this translation helpful? Give feedback.
All reactions