what's the disadvantage of namedChunks?

[Justin-Shen]

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

• I have 3 entries: entry-a & entry-b & entry-c

then

• Add a new entry: aa

• as chunk name is ids in production, after I added this new entry, entry-a / entry-b / entry-c‘s chunkhash is also changed. because all this entries' chunk name is changed, from 1 to 2, from 2 to 3....

---

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 ?

[ooflorent]

And it will be removed in webpack 5?

namedChunks will be removed because it is redundant with chunkIds. Here is a simplified representation of how chunkIds works:

optimization.chunkIds = optimization.namedChunks ? "named" : …

[Justin-Shen]

And it will be removed in webpack 5?

namedChunks will be removed because it is redundant with chunkIds. Here is a simplified representation of how chunkIds works:

optimization.chunkIds = optimization.namedChunks ? "named" : …

Thanks! How to set the chunkId in webpack 4 ? Use the hook optimizeChunkIds ?

[ooflorent]

How to set the chunkId in webpack 4 ? Use the hook optimizeChunkIds ?

Unfortunately it is not possible in v4.
This option has landed on next branch (v5).

[smelukov]

This option has landed on next branch (v5).

@ooflorent can you get a link to the source, please?
Want to get more info :)

[ooflorent]

@smelukov Here are the relevant parts:

• https://github.com/webpack/webpack/blob/next/lib/WebpackOptionsDefaulter.js#L238-L247
• https://github.com/webpack/webpack/tree/next/lib/ids

[smelukov]

@ooflorent thank you!
What do you think about #8355 ?

[sokra]

chunkIds: "named" is also available in webpack 4.

webpack/schemas/WebpackOptions.json

Lines 406 to 409 in 2361995

	"chunkIds": {
	"description": "Define the algorithm to choose chunk ids (named: readable ids for better debugging, size: numeric ids focused on minimal initial download size, total-size: numeric ids focused on minimal total download size, false: no algorithm used, as custom one can be provided via plugin)",
	"enum": ["natural", "named", "size", "total-size", false]
	},

[sokra]

There are disadvantages:

• bundle size increases a bit (you probably don't care about a few bytes)
• chunk name (in webpack 5 also module name) information leak into public (not sure if you care)

[sokra]

The advantage of better long term caching will also provided by deterministic chunk ids like @smelukov mentioned.

[webpack-bot]

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.

[alexander-akait]

Answer above, feel free to feedback