fix: prevent stale chunk errors after deploys#458
Merged
Conversation
…e headers HTML pages use no-cache so browsers always fetch fresh markup after a deploy. Hashed _nuxt/* chunks use immutable long-term caching since their filenames change on every build. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
anilgangapersaud-circle
marked this pull request as ready for review
July 16, 2026 15:04
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF Scorecard
Scanned Files |
yitianx00
approved these changes
Jul 16, 2026
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
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.
What
Sets correct HTTP cache headers via Nuxt
routeRules:Cache-Control: no-cache— browsers always fetch fresh markup after a deploy/_nuxt/**chunks:Cache-Control: public, max-age=31536000, immutable— safe to cache forever since filenames are content-hashedWhy
After a production deploy, users with cached HTML referencing old chunk hashes would get a
Failed to fetch dynamically imported module500 error. A hard reload fixed it individually, but the correct fix is ensuring HTML is never stale.Test plan
Cache-Control: no-cache/_nuxt/*.jsresponses includeCache-Control: public, max-age=31536000, immutable🤖 Generated with Claude Code