-
Notifications
You must be signed in to change notification settings - Fork 49.6k
[Flight] Only use debug component info for parent stacks #34431
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
Conversation
|
Comparing: a9410fb...02bcec4 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
|
dea84dc to
8cc64d4
Compare
| for (let i = 0; i < referencedDebugInfo.length; ++i) { | ||
| const debugInfoEntry = referencedDebugInfo[i]; | ||
| if (debugInfoEntry.name != null) { | ||
| (debugInfoEntry: ReactComponentInfo); |
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.
Double checked that Flow starts erroring once we add another union member to ReactDebugInfoEntry with a name property. This type assertion ensures that future us needs to decide whether a new kind of ReactDebugInfoEntry with name should be transferred or not.
8cc64d4 to
02bcec4
Compare
Follow-up to #34229
We use Component debug info to fill in gaps between Fibers in the parent stack (for React DevTools, errorInfo.componentStack, hydration diffs, etc). It's unfortunate that this makes third-party Server Components disappear.
Before:


After: