Server Components + streaming with Suspense boundaries#2
Merged
Conversation
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
1 participant
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.
adds a /streaming route that demonstrates async server components behind their own suspense boundaries, so the shell paints right away and each card streams in as its data settles instead of the whole page blocking on the slowest read. the data comes from a tiny simulated layer built on a request-scoped memoizing loader, basically the react cache() pattern, so two components asking for the same key in one render share a single fetch and a rejection gets cached the same way. tests cover the loader dedup, the fastest-first settle order, and the async components rendered to static markup, plus there's a short writeup on the route about the CLS tradeoff of over-splitting boundaries. kept it to one concern for now.