-
-
Notifications
You must be signed in to change notification settings - Fork 10.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Detect lazy route discovery manifest version mismatches and trigger reloads #13061
Conversation
🦋 Changeset detectedLatest commit: 638e0fa The changes in this PR will be included in the next version bump. This PR includes changesets to release 11 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
451e1f6
to
1ab0914
Compare
if (discoveredPaths.has(path)) { | ||
return; | ||
} | ||
await fetchAndApplyManifestPatches( | ||
[path], | ||
fetcherKey ? window.location.href : path, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reload the current path on fetcher calls, or the next path on navigations
72fbfb4
to
818bc00
Compare
// This will hard reload the destination path on navigations, or the | ||
// current path on fetcher calls | ||
if ( | ||
sessionStorage.getItem(MANIFEST_VERSION_STORAGE_KEY) === |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good call.
@brophdawg11 This is great! We've had this issue on production and this is exactly what we've been waiting for 🥳 |
This adds manifest version mismatch detection and forces a hard reload to get the user session onto the updated deployed version. Similar concept that we use when we hard reload on a route module asset 404.
Closes remix-run/remix#10455
Closes #12951