fix(server): avoid caching .js
assets in development to fix HMR for safari
#9034
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.
Types of changes
Description
This PR turns off caching for webpack-processed JS files in dev mode.
Fixes reload loop on safari (closes #3828).
Previously, `runtime.js` was being cached in-memory by Safari and triggering infinite HMR updates in the following situation: * server started * change made to file (triggering HMR) * server restarted * safari hard reload -> starts infinite loop (because `runtime.js` from first server is loaded from memory)
Note: if you have previously experienced an infinite reload loop, you will need to clear your Safari cache once using
Develop...Empty Caches
and then reload.Checklist: