-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Document browser-only rendering #8582
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.
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
gnoff
wants to merge
1
commit into
main
Choose a base branch
from
jstory/browser
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,179 @@ | ||
| --- | ||
| title: browser | ||
| version: canary | ||
| --- | ||
|
|
||
| <Canary> | ||
|
|
||
| **The `browser` API is currently only available in React’s Canary and Experimental channels.** | ||
|
|
||
| [Learn more about React’s release channels here.](/community/versioning-policy#all-release-channels) | ||
|
|
||
| </Canary> | ||
|
|
||
| <Intro> | ||
|
|
||
| `browser` lets you skip rendering part of a React tree on the server, leaving its nearest Suspense fallback in place until that content renders in the browser. | ||
|
|
||
| ```js | ||
| use(browser(reason?)); | ||
| ``` | ||
|
|
||
| </Intro> | ||
|
|
||
| <InlineToc /> | ||
|
|
||
| --- | ||
|
|
||
| ## Reference {/*reference*/} | ||
|
|
||
| ### `browser(reason?)` {/*browser*/} | ||
|
|
||
| Call `browser` inside [`use`](/reference/react/use) to skip rendering a component on the server and render it in the browser instead: | ||
|
|
||
| ```js | ||
| import { use } from 'react'; | ||
| import { browser } from 'react-dom'; | ||
|
|
||
| function BrowserOnly() { | ||
| use(browser('This component requires browser APIs.')); | ||
| return <BrowserContent />; | ||
| } | ||
| ``` | ||
|
|
||
| During server rendering, `use(browser())` stops rendering the component and renders the fallback of the closest [`<Suspense>`](/reference/react/Suspense) boundary instead. In the browser, it has no effect, so the component renders normally. | ||
|
|
||
| [See more examples below.](#usage) | ||
|
|
||
| #### Parameters {/*parameters*/} | ||
|
|
||
| * **optional** `reason`: A string or function that provides diagnostic information about why rendering should happen only in the browser. React calls a reason function each time a server renderer encounters the value returned by `browser`; it never calls it in the browser. Use a function for values that are expensive to create, such as `() => new Error(...)`. The resulting value becomes the `cause` of the `Error` passed to `onBrowserBailout`. | ||
|
|
||
| #### Returns {/*returns*/} | ||
|
|
||
| `browser` returns an opaque value. Pass this value to `use` in a component, or use it as the reason when [aborting a server render](#aborting-pending-server-rendering-for-the-browser). In the browser, passing this value to `use` returns `undefined`. | ||
|
|
||
| #### Caveats {/*caveats*/} | ||
|
|
||
| * A component that passes a value returned by `browser` to `use` during server rendering must have a `<Suspense>` boundary above it. Otherwise, the entire server render will fail. | ||
| * `browser` is not available in a `react-server` environment. You can use it while server-rendering Client Components, but you cannot import it in a [React Server Component](/reference/rsc/server-components). | ||
| * Calling `browser()` by itself does not check the current environment or affect rendering. To trigger its behavior, pass the return value to `use` or use it to abort a server render. This means you can create the value at module scope and reuse it. | ||
| * To defer a component, pass the value returned by `browser` to `use`. Do not throw the value directly. | ||
|
|
||
| --- | ||
|
|
||
| ## Usage {/*usage*/} | ||
|
|
||
| ### Rendering content only in the browser {/*rendering-content-only-in-the-browser*/} | ||
|
|
||
| Call `use` with the value returned by `browser` to skip rendering a component on the server: | ||
|
|
||
| ```js | ||
| import { Suspense, use } from 'react'; | ||
| import { browser } from 'react-dom'; | ||
|
|
||
| function BrowserOnlyEditor() { | ||
| use(browser('The editor requires browser APIs.')); | ||
| return <Editor />; | ||
| } | ||
|
|
||
| export default function Page() { | ||
| return ( | ||
| <Suspense fallback={<p>Loading editor...</p>}> | ||
| <BrowserOnlyEditor /> | ||
| </Suspense> | ||
| ); | ||
| } | ||
| ``` | ||
|
|
||
| During server rendering, React includes the `Loading editor...` fallback in the HTML. When the app renders in the browser, `use(browser())` continues immediately and React renders the `Editor` instead. | ||
|
|
||
| --- | ||
|
|
||
| ### Conditionally rendering in the browser {/*conditionally-rendering-in-the-browser*/} | ||
|
|
||
| Like other calls to [`use`](/reference/react/use), `use(browser())` can be called conditionally, including inside a custom Hook. For example, you can wrap a Suspense-enabled data-fetching library's `useQuery` to render initial data on the server, but defer to the browser when that data is missing: | ||
|
|
||
| ```js {3} | ||
| function useBrowserQuery(query, options) { | ||
| if (options.initialData === undefined) { | ||
| use(browser('useBrowserQuery: No initial data was provided.')); | ||
| } | ||
|
|
||
| return useQuery(query, options); | ||
| } | ||
|
|
||
| function ProductDetails({ productId, initialData }) { | ||
| const product = useBrowserQuery(`/api/products/${productId}`, { | ||
| initialData, | ||
| }); | ||
|
|
||
| return <h1>{product.name}</h1>; | ||
| } | ||
| ``` | ||
|
|
||
| On the server, `useBrowserQuery` calls the underlying `useQuery` only when `initialData` is available. Otherwise, `use(browser())` leaves the nearest Suspense fallback in the HTML. In the browser, `use(browser())` continues immediately, so the query library can fetch the data or read it from its client cache. | ||
|
|
||
| --- | ||
|
|
||
| ### Reporting browser-only rendering on the server {/*reporting-browser-only-rendering-on-the-server*/} | ||
|
|
||
| Provide `onBrowserBailout` to the server renderer to report browser-only rendering. React does not report a browser-only render recovered by a Suspense boundary to the server renderer's `onError` callback or [`hydrateRoot`'s `onRecoverableError`](/reference/react-dom/client/hydrateRoot#error-logging-in-production) callback. This example also passes an optional reason, which React makes available as the reported error's `cause`: | ||
|
|
||
| ```js | ||
| import { Suspense, use } from 'react'; | ||
| import { browser } from 'react-dom'; | ||
| import { renderToPipeableStream } from 'react-dom/server'; | ||
|
|
||
| function BrowserOnlyEditor() { | ||
| use(browser(() => new Error('The editor requires a browser API.'))); | ||
| return <Editor />; | ||
| } | ||
|
|
||
| const { pipe } = renderToPipeableStream( | ||
| <Suspense fallback={<p>Loading editor...</p>}> | ||
| <BrowserOnlyEditor /> | ||
| </Suspense>, | ||
| { | ||
| onShellReady() { | ||
| pipe(response); | ||
| }, | ||
| onBrowserBailout(error, errorInfo) { | ||
| logBrowserBailout(error, errorInfo); | ||
| } | ||
| } | ||
| ); | ||
| ``` | ||
|
|
||
| `onBrowserBailout` receives two arguments: | ||
|
|
||
| 1. An `Error` describing the browser-only render. If a reason was supplied to `browser`, it is available as the error's `cause`. | ||
| 2. An `errorInfo` object containing the `componentStack` of the browser-only render. | ||
|
|
||
| The reason function can return any value. Returning a new `Error` gives the cause its own stack without creating that `Error` during rendering in the browser. React does not serialize the reason into the HTML. | ||
|
|
||
| If there is no Suspense boundary to provide a fallback, the server render fails. React reports the failure through the renderer's normal error callbacks instead of `onBrowserBailout`. | ||
|
|
||
| --- | ||
|
|
||
| ### Aborting pending server rendering for the browser {/*aborting-pending-server-rendering-for-the-browser*/} | ||
|
|
||
| You can pass the value returned by `browser` as the reason for aborting a server render. This leaves pending Suspense boundaries in their fallback state so React can render their content in the browser: | ||
|
|
||
| ```js {1,8} | ||
| import { browser } from 'react-dom'; | ||
| import { renderToPipeableStream } from 'react-dom/server'; | ||
|
|
||
| const { pipe, abort } = renderToPipeableStream(<App />, { | ||
| onShellReady() { | ||
| pipe(response); | ||
| setTimeout(() => { | ||
| abort(browser('The server render timed out.')); | ||
| }, 10000); | ||
| } | ||
| }); | ||
| ``` | ||
|
|
||
| Unlike other abort reasons, a value returned by `browser` is not reported to the server renderer's `onError` callback or to `hydrateRoot`'s `onRecoverableError` callback. The server renderer reports each recovered Suspense boundary to `onBrowserBailout` instead. | ||
|
|
||
| For server rendering APIs that accept an [`AbortSignal`](https://developer.mozilla.org/en-US/docs/Web/API/AbortSignal), pass `browser()` as the reason to [`AbortController.abort`](https://developer.mozilla.org/en-US/docs/Web/API/AbortController/abort). | ||
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
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
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this example need a "use client" here?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
react-domis a "client" library in the sense that it is for browser (react-dom/client) and render-for-browser-as-html (react-dom/server). You can use this in frameworks that don't even support RSC so I don't think the examples should imply that this is in any associated with RSC even if it is true that in an RSC framework you can't use this API in Server Components.It's also not the case that you need "use client" on every file that is part of the client bundle, you only need this in files that you want to import into the server as references
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is my main concern:
use(browser())must be a client component; this page does not explicitly call it out, although it is implied.When working with a traditional client-focused framework (like Next.js Pages Router, TanStack Start),
use(browser())works great.There is a different story for server component frameworks (like Next.js App Router and Waku), where components default to being server components and do not execute code in the browser, so components that have
use(browser())and no other hooks will be treated as server components by default. Thus, they will not render and will error out unless they are client components.use(browser())does not force a client component, like having a hook in it. While"use client"is not needed in every file, I would argue that if you have code that must be in the browser, it should have a"use client"so developers know that code is going into the client and don't have hidden dependencies that could break people's apps.If this example does not use "use client", there should be some explicit callout of how to use
use(browser())in server component frameworks.