Repository navigation
Conversation
Handle optional ready and finished promise rejections without changing the updateCallbackDone promise or its rejection semantics. Add public-navigation regression coverage and a router-core patch changeset.
🦋 Changeset detectedLatest commit: e2af57b The changes in this PR will be included in the next version bump. This PR includes changesets to release 23 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 |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
Fixes #8776
🎯 Changes
startViewTransitiononly returnedupdateCallbackDone, so when the browser skips a transition (two navigations within ~1 frame) the rejectedready/finishedpromises were unhandled (AbortError: Transition was skipped).updateCallbackDoneis returned unchanged, so update errors still propagate.Added
packages/router-core/tests/view-transition.test.ts(navigation with rejectingready/finished, missing optional promises,updateCallbackDoneidentity + rejection). The first test fails without the fix.✅ Checklist
Ran locally:
test:unit,test:types,test:eslint,test:buildfor router-core, react-router, solid-router, vue-router — all pass. TheviewTransitione2e tests couldn't launch Chromium in my sandbox, so they were not run.🚀 Release Impact
AI disclosure: the change and test were drafted with an AI coding agent (Codex) and reviewed before submitting.
Summary by CodeRabbit