Redeploy removes prior asset bundles, breaking open sessions
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 610
- Forks
- 62
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 3
Description
Problem statement
Each deploy emits new content-hashed bundles and the previous ones stop being served. A browser tab that was open before the deploy will request a chunk that no longer exists and fail, with no built-in recovery.
Evidence. Cache headers are correct, so this is not a caching bug. See Checked and found working. The failure mode is asset lifetime, not cache policy. We did not manage to reproduce the blank page during this round of work, so this needs a clean repro before filing.
Impact. In an app deployed during working hours, users with an open tab hit a broken lazy load until they reload.
Proposed solution
Retain the previous deployment's assets for a grace period. Separately, document a client-side chunk-load-error handler that triggers a reload, since that pattern is needed regardless.
Alternatives considered
No response
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. First establish a clean reproduction of a pre-deploy browser tab requesting a removed chunk, then trace the deployment asset-retention behavior. Done means previous deployment assets remain available for a defined grace period and the client-side chunk-load-error recovery pattern is documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- infrastructure, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100