-
Notifications
You must be signed in to change notification settings - Fork 47.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Include error name in error chunks #32157
Conversation
} | ||
|
||
export type ReactErrorInfoDev = { | ||
+digest?: string, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We currently don't transport the digest in error values. I don't see why we shouldn't.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be awkward with undefined
vs not defined and it didn't really come up yet anyway.
Comparing: b000019...6cdf20c Critical size changesIncludes critical production bundles, as well as any change greater than 2%:
Significant size changesIncludes any change greater than 0.2%: Expand to show
|
3f1eb7e
to
d4b0a1e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
Follow-up to #32116
resolveErrorDev
is used for error values and error chunks. However, https://github.com/facebook/react/pull/32116only included the name in error values so error chunks were deserialized with anundefined
name e.g. when we fail to serialize the error message-- https://github.com/vercel/next.js/actions/runs/12872159135/job/35887113469?pr=75110#step:32:302
Included some types for error info that are shared between Client and Server to avoid these bugs where we only consider error values and not chunks in the future.