Repository navigation
fix(react): Don't crash ErrorBoundary when error.cause is not an Error - #25542
Merged
andreiborza merged 1 commit intoOct 21, 2026
Merged
andreiborza merged 1 commit into
andreiborza merged 1 commit into
Conversation
4ktLuffy
requested review from
chargome and
s1gr1d
and removed request for
a team
October 19, 2026 19:18
timfish
approved these changes
Oct 21, 2026
51 tasks
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
3 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.
When the caught error has a
causethat isn't an Error, e.g.new Error('x', { cause: 'timeout' }),setCausetried to set.causeon that value. For a string this throws, so the boundary never shows its fallback and the original error is never captured. It now stops at a non-Error cause, which LinkedErrors can't link anyway.Follow-up to #6167, which covered thrown non-Error values but not non-Error causes.