-
-
Notifications
You must be signed in to change notification settings - Fork 387
Feature request: Transforming CSS after CSS is extracted #133
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
Comments
|
I can't find any docs for combining webpack with postcss-modules. It looks like I should stick with my current approach for now while I wait for the new docs. Thanks for the response! |
Some time ago I stumbled on https://github.com/mistakster/postcss-pipeline-webpack-plugin which solves my original issue and has been working nicely, so I'm closing this. |
Hi,
I am using this plugin in combination with CSS modules, and postcss with postcss-autoreset, With the recommended loader chain, autoreset is applied to each imported CSS module, rather than once at the end. When combined with
composes
, this means that the autoreset rules can be applied out of order.Stripped-down example of my issue:
The
color: inherit
for.bar
comes after thecolor: red
, so unfortunately overrides it, and the color will not be red. I was able to solve this by running postcss on the combined, extracted CSS, rather than individually on each input. Unfortunately I had to break out of webpack to do it:And the output is now correct (and more efficient as well!)
Is running a post-extraction transform something that is in scope for this plugin? Is there an existing way to do this as part of the loader chain that I missed?
The text was updated successfully, but these errors were encountered: