-
Notifications
You must be signed in to change notification settings - Fork 10
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
Any plan for you to support MiniCssExtractPlugin for Webpack 4? #10
Comments
I think it should just work |
I am messing around with linaria and my css isn't reloading on changes. Looking around for potential solutions I saw this but am getting some warnings:
If extracted-loader is still recommended, it would probably be good to make it work with mini-css-extract-plugin. |
@nodabladam I can try to fix it if you setup example repository that reproduces issue |
@sheerun For me when I just run the current with-next example here without any changes (other than adding cross-env to build) I get the problem trying to build:
|
current example is probably out of date, I'd need to create new one from scratch |
As per per extract-text-webpack-plugin readme "Since webpack v4 the extract-text-webpack-plugin should not be used for css. Use mini-css-extract-plugin instead."
This plugin might become absolute as a result, been enjoying using it when matching animations to load times and the like. Thanks for contributing to the community.
The text was updated successfully, but these errors were encountered: