Claudio Semeraro

This is compatible with what I'm seeing in a large, multi entries app when I upgrade. Building is a bit slower (~18s to ~22s), rebuilding in watch mode is up...

@alexander-akait I see non-trivial improvements in CPU and memory usage using split chunks in development with webpack4. Anyways, taking `optimization` out in dev mode changes nothing (I rm -rf node_modules...

On splitChunks in dev mode I see other people ran into the same issue and used the same solution: https://github.com/webpack/webpack/issues/8644#issuecomment-455493564 > My reason was that when you have chunking-by-default enabled,...

Updated to the latest version for webpack, webpack-cli and then simply re-saving the same file while webpack is in watchmode webpack 4 ~800ms: ``` [webpack.Progress] 125ms building [webpack.Progress] 13ms finish...

Yes, the only updates to the configuration are necessary to the upgrade to v5. Nothing structural has changed.

Absolutely! ``` { "entry":{ ...multiple entries }, "output":{ "path":"/Users/claudio/Projects/loom/dist/webpack", "publicPath":"https://cdn.loom.com/assets/", "filename":"js/[name]-[contenthash].js" }, "devtool":false, "module":{ "rules":[...rules] }, "optimization":{ "moduleIds":"hashed", "splitChunks":{ "cacheGroups":{ "default":false, "commons":{ "name":"commons", "test":{ }, "chunks":"all", "minChunks":3 } } },...

Oh that's very interesting. I can intuitively understand why would it be a performance drain, do you have any links where I can learn more (multi entry webpack)? 🙏 I'll...

@wuweiweiwu ping :)