Skip to content

It looks like with webpack@4 we can drop "extract-css-chunks-webpack-plugin" in favor of build-in webpack "mini-css-extract-plugin" #22

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.

Sign up for GitHub

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

Jump to bottom
Closed
birdofpreyru opened this issue Jul 3, 2018 · 0 comments
Closed

It looks like with webpack@4 we can drop "extract-css-chunks-webpack-plugin" in favor of build-in webpack "mini-css-extract-plugin" #22

birdofpreyru opened this issue Jul 3, 2018 · 0 comments
Assignees
@birdofpreyru

Comments

@birdofpreyru
Copy link
Collaborator

birdofpreyru commented Jul 3, 2018 •
edited
Loading

I believe, internally, the last version of extract-css-chunks-wepback-plugin anyway relies on mini-css-extract-plugin, thus getting rid of the first will optimize the builds.
@birdofpreyru birdofpreyru self-assigned this Jul 3, 2018
birdofpreyru added a commit that referenced this issue Jul 4, 2018
@birdofpreyru
Update of code chunk splitting (AppChunk) code for Webpack@4
74dbf78 
- Switch from `extract-css-chunks-webpack-plugin` to
`mini-css-extract-plugin`, which comes from Wepback team;
- Use Webpack stats to only load those CSS chunks that exist (the
problem is not solved at the client-side yet);
- Fix of styles hot reloading for Webpack@4 compatibility.

Fix for #22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@birdofpreyru birdofpreyru

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@birdofpreyru