This PR enhances the React Server Components documentation by adding an explanation of manual Promise handling in Client Components as an alternative to the use()
hook.
#8004
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.
Problem
The current documentation only demonstrates using the
use()
hook for handling Promises passed from Server Components to Client Components. However, developers can also manually resolve Promises usinguseEffect
anduseState
, which provides more granular control over loading states and error handling.Solution
Added a new Note section in "Async components with Server Components" that:
useEffect
+useState
use()
Changes
use()
documentation while presenting this as an alternative approachThis addition helps developers understand all available patterns for handling async data in React Server Components, enabling them to make informed architectural decisions.