docs(use-shallow): add troubleshooting entry for "Maximum update depth exceeded"#3507
Merged
dbritto-dev merged 2 commits intoJun 3, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
hyun907
changed the title
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
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
2 participants
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.
Related Bug Reports or Discussions
Related: #3228, #3225, #2979, #2864, #2771, #2748, #2962
Summary
The
Troubleshootingsection of theuse-shallowreference page was aTBDplaceholder. New v5 users frequently encounterMaximum update depth exceededwhen selecting multiple store values into an inline object, but there is no docs guidance pointing them touseShallow.Added a troubleshooting entry that explains the root cause (inline object selector creates a new reference every render → equality check always fails → infinite loop), shows the broken pattern, shows the
useShallowfix, shows the alternative (separate selectors), and links to the v5 migration guide.Check List
pnpm run fixfor formatting and linting code and docs