4 ms·
Per https://webpack.js.org/blog/2020-10-10-webpack-5-release/#general-direction https://webpack.js.org/blog/2020-10-10-webpack-5-release/#ge... : - Improve bui
by acemarke 6y ago
Per https://webpack.js.org/blog/2020-10-10-webpack-5-release/#general-direction https://webpack.js.org/blog/2020-10-10-webpack-5-release/#ge... :
- Improve build performance with Persistent Caching.
- Improve Long Term Caching with better algorithms and defaults.
- Improve bundle size with better Tree Shaking and Code Generation.
- Improve compatibility with the web platform.
- Clean up internal structures that were left in a weird state while implementing features in v4 without introducing any breaking changes.
- Prepare for future features by introducing breaking changes now, allowing us to stay on v5 for as long as possible
- randtrain34 6y agoAre there any benchmarks to get a rough idea on how much improvement in all these areas we can expect to get by upgrading?
- xwdv 6y agoThe only benchmark that matters is how much more money you will make from customers after upgrading.
- dmitryminkovsky 6y agoPut that coffee down! Coffee is for closers only.
- lhnz 6y agoI've heard that build performance is actually worse than webpack 4, if you're not using persistent caching. See: https://twitter.com/FredKSchott/status/1314220659984146432 https://twitter.com/FredKSchott/status/1314220659984146432
- nicoburns 6y agoFrom that thread: The benchmark is dominated by terser and SourceMap performance. What you see are different terser configurations. Webpack 4 with compress.passes: 1 and webpack 5 with compress.passes: 2. Enabled SourceMaps makes minimizing extra expensive.