Vendor chunk naming ignores webpackChunkName comments #14000
Unanswered
MilosRasic
asked this question in
Q&A
Replies: 1 comment
-
We intentionally no longer name vender split chunks by the name of the origin chunk. vendor chunks might be shared by multiple chunks, adding a new chunk which shares an existing vendor chunk should not affect the filename/content of the vendor chunk, since this causes unnecessary invalidations. You could restore the old behavior with a custom |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Bug report
What is the current behavior?
For a dynamic import like this
Webpack 5 will generate the following source code chunk for me:
account.e5d772cdaf3c5f18ee93.js
and a vendor chunk that looks something like:
323.fee73acb2259d6f54633.js
If the current behavior is a bug, please provide the steps to reproduce.
webpackChunkName
magic commentoptimization
config or useSplitChunksPlugin
What is the expected behavior?
Previously, with webpack 4, I'd get files that look like:
account.e5d772cdaf3c5f18ee93.js
account~vendor.fee73acb2259d6f54633.js
Other relevant information:
webpack version: 5.50.0
Node.js version: 12.16.2
Operating System: Linux
Additional tools:
Beta Was this translation helpful? Give feedback.
All reactions