fix: disable static file caching in development#3561
Merged
marvinhagemeister merged 1 commit intoOct 21, 2025
Conversation
When running Fresh 2 in development, the ETag caching was leading to incorrect assets being served. I'd often get stale assets from days ago or separate apps. This problem was especially bad with multiple apps that run on the same port. For example, I may work on App A on the default port 5173. Then boot up App B. I'd get assets from App A when I wouldn't want them, leading to a frustrating dev experience.
marvinhagemeister
approved these changes
Oct 21, 2025
Contributor
marvinhagemeister
left a comment
marvinhagemeister
left a comment
There was a problem hiding this comment.
Good catch, thanks!
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
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.
When running Fresh 2 in development, the ETag caching was leading to
incorrect assets being served. I'd often get stale assets from days ago
or separate apps. This problem was especially bad with multiple apps
that run on the same port. For example, I may work on App A on the
default port 5173. Then boot up App B. I'd get assets from App A when I
wouldn't want them, leading to a frustrating dev experience.