firebase / firebase/firebase-tools

Any open tab white screens after hosting re-deploy (Next.js)

Open
#6,676 0 comments 0 reactions 0 assignees View on GitHub
integration: web frameworks type: bug
Dominant language
TypeScript
Stars
4.5k
Forks
1.3k
Avg merge
1d 12h
Merged PRs (30d)
84

Description

### [REQUIRED] Environment info

**firebase-tools:** 13.0.2

**Platform:** macOS

### [REQUIRED] Test case

1. Deploy a simple Next.js site using Firebase hosting.
2. Open it in the browser.
3. Re-deploy site.
4. Go back to the open browser tab.

### [REQUIRED] Steps to reproduce

See above.

### [REQUIRED] Expected behavior

The app should either continue running as it was (with stale assets), refresh to get all new assets, or show a user-visible error.

(I get that this may be more in the domain of Next.js framework behavior and not so much up to the hosting provider, but Firebase could likely provide more support here. For instance, persist stale chunks on the server for a few extra days, or configure the Next.js app on `firebase init` to be more resilient, if any such option is available.)

### [REQUIRED] Actual behavior

Existing open tab becomes white screen, probably in response to a failed fetch request. Console reads: "404, failed to fetch chunk," or something to that effect. `location.reload()` successfully reloads the site.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.