[Flight] Serialize Server Components Props in DEV #31105
Merged
+245
−97
Conversation
This file contains 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
…alue serialization
…ng very large props console.log:ed objects can have a higher limit since they are explicit where as props of Server Components is not something you can limit yourself.
This is not strictly necessary but it ensure they get the right props etc
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
facebook-github-bot
added
CLA Signed
React Core Team
gnoff
approved these changes
Sep 30, 2024
| request.pendingChunks++; | ||
| const id = request.nextChunkId++; | ||
|
|
||
| // We can't serialize the ConsoleTask/Error objects so we need to omit them before serializing. |
There was a problem hiding this comment.
didn't you just land this in a different PR?
There was a problem hiding this comment.
This is a different kind of Error object. One used for the JSX stack. It doesn't have the original stack.
Still not great because it should really block listeners on the row itself so that we have all the debug info before resolving the promise. It also doesn't handle debug info in the right order.
This was referenced Oct 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This allows us to show props in React DevTools when inspecting a Server Component.
I currently drastically limit the object depth that's serialized since this is very implicit and you can have heavy objects on the server.
We previously was using the general outlineModel to outline ReactComponentInfo but we weren't consistently using it everywhere which could cause some bugs with the parsing when it got deduped on the client. It also lead to the weird feature detect of
isReactComponent. It also meant that this serialization was using the plain serialization instead ofrenderConsoleValuewhich means we couldn't safely serialize arbitrary debug info that isn't serializable there.So the main change here is to call
outlineComponentInfoand have that always write every "Server Component" instance as outlined and in a way that lets its props be serialized usingrenderConsoleValue.