-
-
Notifications
You must be signed in to change notification settings - Fork 8.7k
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 5: deterministic output, better build performance and caching #4027
Comments
|
It's something I wanted to work on just after the i18n release, so tell me on discord if you give it a try :) I think we can split the work in multiple parts, like the minimum upgrade, and another PR for perf/caching improvements |
If It's useful for anyone, I reviewed the dependencies that are related to webpack:
|
Progress reportIn my PR, I have successfully repaired development and production builds. DependenciesThis change requires updating a ton of dependencies. It has also added, removed and changed a few, such as: - pnp-webpack-plugin
* @endiliey/responsive-loader -> responsive-loader-modern (my fork, stops webpack from throwing due to a webpack 2 backwards compatibility check that breaks things)
* optimize-css-assets-webpack-plugin -> css-minimizer-webpack-plugin (see note below!)
* react-loadable-ssr-addon -> react-loadable-ssr-addon-webpack-5 (also my fork, stops it from trying to use chunk data that is no longer exposed) SpeedI have not measured speed impact/changes yet. |
We are anxiously awaiting this as we have recently migrated our monorepo to Webpack 5, and our Docusaurus styleguide is the one project that's keeping us from making it a complete migration. Thanks for all the work that's being done on this! |
You don't need |
Yeah we removed that |
@anshulrgoyal by the way, its 0.5 seconds faster after the upgrade. I did this benchmark on different, identically powerful machines, with no caches. |
🚀 Feature
We should upgrade to Webpack 5 for various reasons
(just creating the issue to reference it in blog post).
Related to this issue with undeterministic static output: #3383
The text was updated successfully, but these errors were encountered: