-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Upgrade to Webpack 4.0 #1549
Comments
where are you specifying the |
@joemewes In the webpack config itself. |
Have you tested BundleAnalyzerPlugin after this PR? webpack-contrib/webpack-bundle-analyzer#159 |
* Updated for webpack 4 * Updated start.js with webpack 4 hooks API * Removed NoEmitOnErrorsPlugin and NamedModulesPlugin * Updated Layout.test to have mocked pathname in context * Removed "assets-webpack-plugin" in favour of "webpack-assets-manifest" * Changed `vendor.js` → `vendors.js` — naming consistency with webpack * `assets.json` → `asset-manifest.json` * new file `chunk-manifest.json` for SSR support Closes #1562, #1549
* Updated for webpack 4 * Updated start.js with webpack 4 hooks API * Removed NoEmitOnErrorsPlugin and NamedModulesPlugin * Updated Layout.test to have mocked pathname in context * Removed "assets-webpack-plugin" in favour of "webpack-assets-manifest" * Changed `vendor.js` → `vendors.js` — naming consistency with webpack * `assets.json` → `asset-manifest.json` * new file `chunk-manifest.json` for SSR support Closes kriasoft#1562, kriasoft#1549
Well Webpack 4.0 is out and it is of course awesome, so we need an upgrade.
Things to ook out for:
There is probably more but these are the first things that I saw that needed to be addressed I think.
UPDATE:
So far I have it working, but there is a weird bug in BundleAnalyzerPlugin where it cannot analyse the "shared" bundle. Not sure why but probably has to do something with JSONP
I'll make an PR soon with the "bug" in there.
The text was updated successfully, but these errors were encountered: