Fix broken anchor link for async components on the client - #8484
Open
LuxologyGG wants to merge 1 commit into
Open
LuxologyGG wants to merge 1 commit into
LuxologyGG wants to merge 1 commit into
Conversation
Size changesDetails📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
LuxologyGG
marked this pull request as ready for review
June 19, 2026 02:58
cursor
Bot
force-pushed
the
fix/auto-issue-7305
branch
from
July 1, 2026 19:04
a2c9206 to
f046ad4
Compare
cursor
Bot
force-pushed
the
fix/auto-issue-7305
branch
from
July 10, 2026 19:03
f046ad4 to
8577826
Compare
Add the missing 'Why can't I use async components on the client?' section and link to it from the async components example. Fixes reactjs#7305
LuxologyGG
force-pushed
the
fix/auto-issue-7305
branch
from
August 21, 2026 19:09
8577826 to
1639b0b
Compare
This branch was successfully deployed
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
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.
Summary
Closes #7305
The Server Components page states that async components are not supported on the client, but it does not define the referenced
#why-cant-i-use-async-components-on-the-clientsection, so that in-page destination is missing.This PR links the phrase "not supported on the client" to a new
Notethat explains why async components are a Server Component feature and how to useuse()on the client instead.Before / After
Before: Plain sentence with no link and no matching section:
Since async components are not supported on the client, we await the promise with use.After: The phrase links to a new
Notetitled "Why can't I use async components on the client?" with the anchor{/*why-cant-i-use-async-components-on-the-client*/}.Type of change