New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Postcss @import glob support #12336
Comments
I think we could internally support the |
Since |
related: #10079 |
Interesting, maybe rewriting the plugin with Postcss 8's plugin would solve this issue, so we don't have to carve out an API to put plugins before Vite's (which I'm not sure how without non-standard plugin properties). I guess one upside of having this builtin is support for globbing with aliases 🤔 |
@bluwy I would like to work on this issue |
What about |
in the meantime you can use import.meta.glob in your main.js file to include all the css files of a folder as suggested here #6688 (comment) by Knovour |
Description
Vite currently uses
postcss-import
to resolve@import
, there are some postcss plugins out there that supports glob imports like:But they can't be used as they can't be injected before Vite's
postcss-import
plugin instance. Vite also adds it's custom resolve logic (alias, extension, export conditions, etc), sopostcss-import
can't be swapped out.Suggested solution
Ideally a first-class support would prevent needing a new API for injecting plugins before
postcss-import
.It could look like
postcss-import-ext-glob
using@import-glob
, as it's also a suggested plugin inpostcss-import
's readme.Alternative
No glob support. Or support injecting plugins before
postcss-import
.Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: