-
Notifications
You must be signed in to change notification settings - Fork 19
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
Class names that are not valid JS identifiers are excluded from Webpack bundle #294
Comments
This came about because of the change to ES2015 exports in #282, seems like it's related to webpack/webpack#4742 |
I may need to revert the change to use ES2015 exports, will see which API is more annoying. Having to /cc @TrySound as the source of the request for ES2015 exports to hear another perspective. |
@kevinkace Using Maybe this should be a breaking change, but this is the right way. |
@tivac Not a bug. Just two different module systems. |
Webpack guys force to use es modules and rewrites loaders with them, so why should we step back? |
Current plan is to add a Hoping to get this work completed tonight. There are plenty of legitimate reasons to still use commonjs, so it needs to be supported in a reasonable & compatible way. |
Yeah, it's good, but disabled by default :) |
This is in |
CSS class names are exported differently in a webpack bundle depending if the class names are valid JS identifiers or not. Invalid class names are only included under
.default
.Test repo: https://github.com/kevinkace/webpackTest
The text was updated successfully, but these errors were encountered: