-
-
Notifications
You must be signed in to change notification settings - Fork 384
CssModule context property is null in v0.8.1 #473
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
We don't touch this code in |
Here you go: https://github.com/i-like-robots/broken-css-extract-plugin If you run Install v0.8.0 of this plugin ( Hope that helps! |
@i-like-robots what about |
We can do that but I'm concerned that a public part of this module's interface has changed unexpectedly. I assume this may cause other users a problem as well 😱 |
Thank you @evilebottnawi - much appreciated 🙇 |
Expected Behavior
We have implemented code splitting in our apps which uses each module's
context
property to decide whether they should be extracted into separate chunk. We have used this configuration for some time but has broken when using v0.8.1 of this package.Actual Behavior
The
context
property for instances ofCssModule
isnull
instead of a string as we expect so our Webpack compilation fails. e.g.:Code
Here is an example configuration for enabling code splitting using
module.context
:How Do We Reproduce?
Try adding the code splitting configuration shown above to a project using this plugin and a CSS entry point (or try any configuration which expects
module.context
to be a string).EDIT: test repo here https://github.com/i-like-robots/broken-css-extract-plugin
The text was updated successfully, but these errors were encountered: