You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FEATURE REQUEST: improve documentation to migrate from webpack 3 and CommonsChunkPlugin to webpack 4 and SplitChunksPlugin
What is the current behavior?
Documentation only addresses very simple cases.
What is the expected behavior?
I have a two heavy pages with loads of components called 'editor' and 'player' and a multitude of light pages with standard components essentially for input and grid. Accordingly, my webpack 3 configuration consists of an entry per page including 'editor' and 'player' and two CommonChunkPlugin:
I load common.bundle.js on all pages and heavy.bundle.js only on the 'editor' and 'player' pages with the additional required components.
I have found the following way to migrate this configuration to webpack 4 and SplitChunksPlugin but this is undocumented. Is this equivalent? Any caveat?
Do you want to request a feature or report a bug?
FEATURE REQUEST: improve documentation to migrate from webpack 3 and CommonsChunkPlugin to webpack 4 and SplitChunksPlugin
What is the current behavior?
Documentation only addresses very simple cases.
What is the expected behavior?
I have a two heavy pages with loads of components called 'editor' and 'player' and a multitude of light pages with standard components essentially for input and grid. Accordingly, my webpack 3 configuration consists of an entry per page including 'editor' and 'player' and two CommonChunkPlugin:
I load common.bundle.js on all pages and heavy.bundle.js only on the 'editor' and 'player' pages with the additional required components.
I have found the following way to migrate this configuration to webpack 4 and SplitChunksPlugin but this is undocumented. Is this equivalent? Any caveat?
If this is a feature request, what is motivation or use case for changing the behavior?
I am not the only one to struggle with this undocumented use case: see https://gitter.im/webpack/webpack?at=5ad7a325270d7d3708df7392.
It might be worth documenting...
This issue was moved from webpack/webpack#7085 by @montogeek. Original issue was by @jlchereau.
The text was updated successfully, but these errors were encountered: