BC-8017 - Enable Cache Busting via Content Hash in Frontend #3395
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.
Short Description
In order to make sure that frontend application code is reloaded in the user's browser when it has been changed we want to enable Cache Busting.
Webpack builds can be configured to write a content hash in the generated file names during build. When the conten has been updated the hash will change and the browser is forced to reload the file.
https://webpack.js.org/guides/caching/
Links to Ticket and related Pull-Requests
BC-8017
Changes
Data-security
Deployment
New Repos, NPM packages or vendor scripts
Screenshots of UI changes
Checklist before merging