Skip to content

Fix broken anchor link for async components on the client #8484

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.

Sign up for GitHub

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

Open
LuxologyGG wants to merge 1 commit into
base: main
Choose a base branch
from
+9 −1
Open

Fix broken anchor link for async components on the client #8484

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion src/content/reference/rsc/server-components.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -293,4 +293,12 @@ function Comments({commentsPromise}) {

The `note` content is important data for the page to render, so we `await` it on the server. The comments are below the fold and lower-priority, so we start the promise on the server, and wait for it on the client with the `use` API. This will Suspend on the client, without blocking the `note` content from rendering.

Since async components are not supported on the client, we await the promise with `use`.
Since async components are [not supported on the client](#why-cant-i-use-async-components-on-the-client), we await the promise with `use`.

<Note>

#### Why can't I use async components on the client? {/*why-cant-i-use-async-components-on-the-client*/}

Async components are a Server Component feature. Client Components need to run synchronously so they can use Hooks and respond to interactions. To wait for async data on the client, pass a Promise from a Server Component and read it with [`use`](/reference/react/use) instead.

</Note>
Loading