-
-
Notifications
You must be signed in to change notification settings - Fork 8.8k
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
what's the disadvantage of namedChunks? #8354
Comments
optimization.chunkIds = optimization.namedChunks ? "named" : … |
Thanks! How to set the chunkId in webpack 4 ? Use the hook optimizeChunkIds ? |
Unfortunately it is not possible in v4. |
@ooflorent can you get a link to the source, please? |
@ooflorent thank you! |
webpack/schemas/WebpackOptions.json Lines 406 to 409 in 2361995
|
There are disadvantages:
|
The advantage of better long term caching will also provided by deterministic chunk ids like @smelukov mentioned. |
This issue had no activity for at least half a year. It's subject to automatic issue closing if there is no activity in the next 15 days. |
Answer above, feel free to feedback |
In production mode, namedChunks is default to false, so what is the disadvantage of namedChunks, I think it is necessary in production.
webpack version: 4.25.1
e.g.
before
then
The outcome was undesired !
I think when I add a new entry, all the existed entries' chunkhash will not be changed. Or the cache will be failed, even though their contents have not changed.
To resolve this problem is add
optimization.namedChunks: true
in production mode.But why it is default to false? Is that any problem?
And it will be removed in webpack 5 ?
The text was updated successfully, but these errors were encountered: