-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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.0 #1316
Webpack 4.0 #1316
Conversation
It might be a good idea to replace |
Thanks @renchap that's the plan 👍 |
What is the status of this PR? Is there something we can help from webpack side? |
@montogeek Note the blocker in the description. This project relies on plugin that hasn't merged v4 support yet. |
@rossta Already commented on it |
1434d78
to
d2f698e
Compare
package/environments/production.js
Outdated
@@ -11,7 +10,7 @@ module.exports = class extends Base { | |||
|
|||
this.plugins.append( | |||
'UglifyJs', | |||
new UglifyJsPlugin({ | |||
new webpack.optimize.UglifyJsPlugin({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This won't work with ES6 modules
1b9c77f
to
9b9b309
Compare
This PR is going to take a while since the plugin and loader support isn't 100% yet - the main blockers are manifest and vue loader, everything else seems to be working fine. Will release a beta once this PR is merged and then we can incrementally enhance in separate PRs until stable 4.0.x |
9b9b309
to
7b553b4
Compare
7b553b4
to
01c09b4
Compare
Just published a pre-version: To try out:
|
@gauravtiwari any hints on how to get it working / upgrading? |
@apuntovanini Pretty simple and no breaking changes (AFAIK) - just update gem and npm package as above ^^ |
@apuntovanini You might have to run |
:) yep, thats the reason I asked, mine is broken, saying no manifest found. I use CommonsChunkManifest (now deprecated, isn't it?), but even without it doesnt work |
ah, I see, didn't try that, I will try again and let you know ASAP, thanks! |
@apuntovanini Oh yes, that's true. Please see this gist on how to migrate common chunk - https://gist.github.com/sokra/1522d586b8e5c0f5072d7565c2bee693#configurate-cache-groups |
With webpacker it would be, environment.config.merge({
optimization: {
splitChunks: {
cacheGroups: {
commons: {
test: /[\\/]node_modules[\\/]/,
name: 'vendors',
chunks: 'all'
}
}
}
}
}) |
Wonderful, it does work ( |
when is the non pre release version coming? |
I see |
@gauravtiwari Any timeline for moving 4.x to stable? If there is a clear checklist/roadmap I'm sure there are a good few of us who will help out! |
@danielpowell4 Thanks, basically it's nearly there. I have made this PR (#1546) a while ago but couldn't finish it, apologies :( Will try to get this done over the weekend and see if I can publish a stable release next week. |
@gauravtiwari no need to apologize! Timeline sounds awesome. I have been on the pre version since it came out. Only recently ran into a snag when I went to tweak my babel config. If you need help writing docs or monitoring the repo, feel free to reach out! |
What's involved in getting 4.x released? Happy to assist. |
@gauravtiwari Any updates? I'm sure some like @iChip are willing to lend a hand if possible! |
Hey, Sorry, I need to find sometime to review some PRs like: #1694 and go through this big list of issues: https://github.com/rails/webpacker/issues to see if we have missed anything obvious that should be in 4.x stable release. What if I release a beta 4.x version? Would that help time being? |
Just made another pre-release:
|
Also, now Rails 6.0-alpha ships with Webpacker as default- https://github.com/rails/rails |
This PR adds webpack 4.0 support to Webpacker.
TODO:
Blockers