-
Notifications
You must be signed in to change notification settings - Fork 12k
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
feat: update to webpack 4 #9459
Conversation
@pleerock can you try with this PR? |
fabd7fd
to
674e16f
Compare
Easiest way to experiment is to start with an existing project then separately:
|
It works fast! Running
Which took only 2,5 minutes. Amazing. But I have this error at the end:
Also Im still not able to test what it generate because of blocking issues. |
c0cc4d0
to
a9b80cf
Compare
fadcb0f
to
2e64c44
Compare
b7a7cc1
to
713db88
Compare
0b005f4
to
2654d2d
Compare
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.
Great work @clydin! The changes overall LGTM, but can you add a comment in this PR with the followup actions needed?
There's a few here and I worry we'll loose track of them if we don't have an explicit list to followup.
I also see warnings on builds like
I think they are from the bad peerdeps, can you confirm? |
The deprecation warnings are from plugins that haven't been updated to use the new v4 plugin system. Some of the CLI's still need updates but we can transition them in additional PRs. Also, we'll have to wait for updates to the some of the webpack dependencies used to fully clear out the warnings. The schema warnings are due to the Webpack update to ajv 6 and webpack not updating the corresponding internal schemas. Updating to beta.2 removed some of them. |
2654d2d
to
f9d761a
Compare
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.
I didn't mean to review, just asking.
"file-loader": "^1.1.5", | ||
"fs-extra": "^4.0.0", | ||
"glob": "^7.0.3", | ||
"html-webpack-plugin": "^2.29.0", | ||
"html-webpack-plugin": "github:webpack-contrib/html-webpack-plugin#a8a8c2b6ea496c257fd6f501db3a06a51fa03e1e", |
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.
The PR says "CLI internal index html plugin used" #9459 (comment).
Why do we need the html-webpack-plugin then? Is it only a temporary fix?
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.
See text below headline „🛑 If you use HtmlWebpackPlugin“ on https://medium.com/webpack/webpack-4-released-today-6cdb994702d4
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.
Yes, I know this. But @clydin wrote "CLI internal index html plugin used" instead, that is why I am asking.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
WIP PR to upgrade to Webpack 4.0.0-beta.2 (changelog).
Based on the work in #8611 by @filipesilva
NOTE:
ng eject
is broken and will be addressed in a followup PR.Additional actions after merging:
commonChunks
option. Webpack now has much more sophisticated chunk splitting logic by default.Blocking Issues:
Version 4.4.1 releasedcopy-webpack-plugin
(fix(index): addwebpack >= v4.0.0
support webpack-contrib/copy-webpack-plugin#212 approved; waiting on next release)webpack v4 migration plan jantimon/html-webpack-plugin#816 (PR at Webpack v4.0.0-alpha support jantimon/html-webpack-plugin#823)CLI internal index html plugin usedWebpack 4 compatibility webpack-contrib/extract-text-webpack-plugin#7014.0.0-alpha.0 released with initial Webpack 4.0 supportNote that due to the following warnings, there may still be additional issues with specific features.
Peer Dependency Warnings: