Use cache-busting Webpack chunk names in development #2920
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
williamjallen
force-pushed
the
webpack-chunk-caching
branch
from
faa6247 to
0e6be30
Compare
williamjallen
force-pushed
the
webpack-chunk-caching
branch
from
0e6be30 to
a266c83
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#2864 introduced Webpack bundle splitting. While the chunk names are based on a rolling integer number in production, they are deterministically computed based on the filename in development. Browser caching causes this to be annoying in development. This PR changes the naming scheme to instead depend on the content hash, eliminating the issue.