-
Notifications
You must be signed in to change notification settings - Fork 85
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
webpack 4 support #60
Comments
For information, I modified a little the code present here: chunks.forEach(function(chunk, i) {
var extractedChunk = extractedChunks[i];
extractedChunk.index = i;
extractedChunk.originalChunk = chunk;
extractedChunk.name = chunk.name;
extractedChunk.groupsIterable = chunk.groupsIterable;
// chunk.chunks.forEach(function(c) {
// extractedChunk.addChunk(extractedChunks[chunks.indexOf(c)]);
// });
// chunk.parents.forEach(function(c) {
// extractedChunk.addParent(extractedChunks[chunks.indexOf(c)]);
// });
}); And I have no more errors. The new
|
One more information. I still don't understand very well what does extract-css-chunks-webpack-plugin in this scope so I'm not sure how to create the migration. I hope all these informations will help :) |
thanks @GuillaumeCisco . This is a good start to diagnosing what must be done. I guess once |
I've just tested with the last version of |
It looks like extracting CSS chunks will be supported in webpack 4 via https://github.com/webpack-contrib/mini-css-extract-plugin |
Yup! |
Does this mean this issue can be closed @GuillaumeCisco ? |
Unfortunately not @davidfurlong . Furthermore the port towards webpack 4 from @izaakschroeder is still not finished #61 Maybe we should wait a bit further. |
@faceyspacey any estimated timeline for webpack 4 support for your package |
if this is gonna do it: https://github.com/webpack-contrib/mini-css-extract-plugin , it doesn't seem like a good use of time unfortunately. |
Ok thanks @faceyspacey |
mini-css-extract-plugin seems to be pretty buggy still, unfortunately. Trying to get it working right now and no matter what I do, my generated css files just don't get rebuilt when I change css. That's sooo annoying. |
Also mini-css-extract-plugin does not support HMR yet. Are there any css extractors that support HMR? |
mini-css-extract-plugin does not support HMR for time being. May use |
Opening pull request soon for webpack 4 support |
@zackljackson one of our users forked it already and made it work (just this week). Maybe talk with him on twitter: https://twitter.com/simon_skiscool/status/996286374578917376 |
Thanks I’ll touch base with him, either this or moving to mini-css-chunk plug-in |
i can just share the code.; it's working just composition between the last webpack-text-chunk@next and some relevant code from extract-css-chunks-webpack-plugin. about mini-css-extract-plugin i used it for other boilerplate, it's work but i'm not enough good to understand how is it and how we can merge it with extract-css-chunks-webpack-plugin |
i create a repo with the code changed. relevant line who do the trick is here on this line: L327 Sorry if i did not test all some mods I just merge on loader.js and index.js from the new webpack-text-plugin@next with the extract-css-chunks-webpack-plugin Who i have to say i have no idea all the effect. I have to say it's amazing what did faceyspacey with his react-component-universal |
Hey Simon Thanks for touch base here! I’ll update our plugin accordingly. When there’s a pittle more time I will also look at mini-css-extract at a later stage and see if it’s worth extending/switching to. It’s not reloading is not well integrated. Thanks again for the share! |
just a comment about the mod: if i use like webpack-text-plugin@next i have got some problem in development mode.. just with extractedChunk.groupsIterable = chunk.groupsIterable; |
Hey guys! I just finished a fully working solution. True hot reloading new files, no style-loader in dev. Pretty much exactly what we want / need / had. I’m looking for beta testers ❤️ I’ll be opening a branch tomorrow for everyone to look at and a PR shortly after. If you can improve it .... PLEASE PR MY BRANCH. Apologies it took long, thank you for your patience and continued support! I know this has been a challenge in the greater FE community. I’ll try and track down the open issues I’ve seen across the internet, but if you know of a project struggling. Let them know |
This comment has been minimized.
This comment has been minimized.
So far @zackljackson solution is working on the dev branch of https://github.com/rherwig/template-react-16-ssr I'm currently looking into testing it in a "real world" progressive web app to see how it behaves using react router, etc... |
This is very encouraging! @rherwig |
@rherwig one thing I realized. I need to add an additional check for production builds Currently it should work fine, but it'll include an extra couple lines of JS for hot loading. Ill likely only release this in a few hours or tomorrow. Let me know how it handles |
@zackljackson @faceyspacey |
+1 Need this badly. |
Okay guys, I’ll look at making a next tag |
@rajatpharmeasy @rherwig @d3viant0ne @dtonys @davidfurlong Enjoy fellas! Ill be pushing updates to this tag from now on, theres very little left to check and do on this side so it'll be merged to master today or tomorrow! https://www.npmjs.com/package/extract-css-chunks-webpack-plugin/v/3.0.0 |
Pull request open 🔥 |
I am so gonna integrate this in my template project as soon as it hits master! Tests have been working out great so far :-) |
@rherwig @rajatpharmeasy @GuillaumeCisco @franjohn21 @davidfurlong 🍾🍾🍾 Will be releasing it tomorrow around 10 am EST 🚀🚀🚀 Please note: you'll want to update both the universal-import babel plugin and this one :) We greatly appreciate your ongoing support and interest in the project. Especially critical feedback received during testing. 🍾🍾🍾 It's our absolute pleasure to provide this update 🚀🚀🚀 Please let us know if theres any issues & PRs are always welcome |
Hey there @faceyspacey
Hope you are doing well.
I was messing around with the next version of webpack i.e
4.0.0-beta.0
and ran into an issue when trying to compile with it.Looks like the exact same problem as webpack-contrib/extract-text-webpack-plugin#701
Let me know if I can help further.
🤙
The text was updated successfully, but these errors were encountered: