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
The medium article in the comment above the splitChunks setting offers some explanation:
Note: Since the chunk name includes all origin chunk names it’s recommended for production builds with long term caching to NOT include [name] in the filenames, or switch off name generation via optimization.splitChunks.name: false. Elsewise files will invalidate i. e. when more chunks with the same vendors are added.
You don't need to know why this option has a certain value.
As CRA user, you don't even need to know what happens after the hood.
If you still need some advanced configuration, then you know all this option.
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.
Is this a bug report?
Not a bug report.
I find these configs in webpack.config.prod.js
The splitChuns.name is false, this seems lead to the vendor chunk name become to something like this:
rather than vender~main.xxxxxx.chunk.js
So, I am confused why set name to false.
The text was updated successfully, but these errors were encountered: