fix: force refresh on chunk preload error

[yangshun]

Pre-flight checklist

• I have read the Contributing Guidelines on pull requests.
• If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
• If this is a new API or substantial change: the PR has an accompanying issue (closes Stale sessions error out during navigate if a deployment occured after the page first loads #7599) and the maintainers have approved on my working plan.

Motivation

Fixes #7599

Test Plan

1. Build the site
2. Do yarn run serve
3. Load https://localhost:3000
4. Kill the server
5. Try to navigate, the page will immediately refresh and show the browser's error page. Previously it won't because we're using client-side navigation and just fail silently with an infinite loading bar

Test links

Deploy preview: https://deploy-preview-_____--docusaurus-2.netlify.app/

Related issues/PRs

[Josh-Cena]

That's nice!

Have you managed to test the fresh deployment case? I'm wondering if it will reload and show the new page, or reloads and show the current page again.

[yangshun]

Have you managed to test the fresh deployment case? I'm wondering if it will reload and show the new page, or reloads and show the current page again.

It will show the new page because the URL has updated already. I'm waiting for the preview build to complete, then change something to trigger another preview build while having a tab open on the previous preview build. Hopefully I can test it this way.

[netlify]

✅ [V2]

Name	Link
🔨 Latest commit	45d3bef
🔍 Latest deploy log	https://app.netlify.com/sites/docusaurus-2/deploys/62a458ef340cfc0008683e1b
😎 Deploy Preview	https://deploy-preview-7600--docusaurus-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[github-actions]

⚡️ Lighthouse report for the deploy preview of this PR

URL	Performance	Accessibility	Best Practices	SEO	PWA	Report
/	🟠 88	🟢 100	🟢 100	🟢 100	🟢 90	Report
/docs/installation	🟠 87	🟢 100	🟢 100	🟢 100	🟢 90	Report

[Josh-Cena]

Nice, I think I've been tricked by this in the past.

[github-actions]

Size Change: +27 B (0%)

Total Size: 801 kB

ℹ️ View Unchanged

Filename	Size	Change
website/.docusaurus/globalData.json	52.6 kB	0 B
website/build/assets/css/styles.********.css	106 kB	0 B
website/build/assets/js/main.********.js	603 kB	+27 B (0%)
website/build/index.html	38.9 kB	0 B

_{compressed-size-action}

[slorber]

hmmm we can give a try but wonder if it will work fine under all conditions

For example what if the user has a temporary bad network?
Trying to reload may not be ideal: maybe in some cases we'll want to keep waiting and set-up some polling 🤷‍♂️

We'll see

[Josh-Cena]

We didn't retry before this anyway. Refreshing is already a form of retry, and if it fails, the user instantly knows something is wrong, instead of getting stuck in an infinite loading bar.

[yangshun]

We didn't retry before this anyway. Refreshing is already a form of retry, and if it fails, the user instantly knows something is wrong, instead of getting stuck in an infinite loading bar.

Was about to say something like this but @Josh-Cena said it better