-
Notifications
You must be signed in to change notification settings - Fork 143
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
some webpack-built files are named with their file hash while others aren't #11670
Comments
whatisgalen
added a commit
that referenced
this issue
Jan 10, 2025
whatisgalen
added a commit
that referenced
this issue
Jan 10, 2025
whatisgalen
added a commit
that referenced
this issue
Jan 10, 2025
whatisgalen
added a commit
that referenced
this issue
Jan 10, 2025
whatisgalen
added a commit
that referenced
this issue
Jan 10, 2025
whatisgalen
added a commit
that referenced
this issue
Jan 10, 2025
11 tasks
whatisgalen
added a commit
that referenced
this issue
Jan 12, 2025
whatisgalen
added a commit
that referenced
this issue
Jan 12, 2025
whatisgalen
added a commit
that referenced
this issue
Jan 12, 2025
whatisgalen
added a commit
that referenced
this issue
Jan 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A common use case is that a developer has updated their project and pushes these updates to a production server (run webpack build, collectstatic, etc.) but end-users' browsers are still caching the old files. There's a cache-bursting strategy built into the logic of how webpack names these files:
The
contenthash
is used in creating the name of each file, capturing its updated state which then forces browsers to get the new files from the server. However whennpm run build_production
gets run, only so-calledchunkFiles
(.chunk.js
) get their content hash mixed into their file names. Files likesearch.js
orgraph.js
do not contain any hash values in the filenames, despite the explicit logic above in the webpack config.The text was updated successfully, but these errors were encountered: