chore(site): update React Query to 5.101.4 - #27937
Draft
ethanndickson wants to merge 2 commits into
Draft
Conversation
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.
Follow-up to #27514.
PR #27514 needed React Query's
mutationOptions, but we were still on5.77.0and the helper was not available until5.82.0. I kept that PR to the minimum version bump it needed because moving all the way to the latest version required code changes. This follow-up finishes that upgrade, taking React Query and its devtools from5.82.0to5.101.4.The newer mutation callback context meant a couple of tests could no longer call the option callbacks directly, so they now run the real lifecycle through
MutationObserver. It also exposed stale placeholder data inusePaginatedQuery; the hook now waits for the active query key before prefetching or correcting an invalid page.React Query now publishes some query updates one microtask later, so a few tests and stories also wait for the rendered state instead of assuming it is synchronous. Pixel exposed one separate
IconFieldstory race already present onmain, so this also waits for the lazy picker before snapshotting.