Conversation
Values a link prefetches and values a navigation computes live in separate places that cannot see each other, which is behind a run of parent props bugs and would need solving again for loaders. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
✅ Deploy Preview for kitbag-router ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This was referenced Jul 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Proposal, not an implementation — nothing here changes behaviour.
A route's values are computed in two places that cannot see each other: what a link prefetches, and what a navigation computes. Whether a child route can use something from its parent depends on which of those two places the parent's value happens to be in, and when. That is the shared cause behind #793, #794, #795, #802 and #803, and loaders will need the same problem solved again.
The RFC proposes one small store that knows nothing about props or loaders, where a value is a promise from the moment it is first asked for, and prefetched and committed values have the same shape.
Worth reading for the sections on what it deliberately does not do (deduplication, reference counting) and on sequencing — the current stack of fixes should land first, for its tests rather than its fixes.