Skip to content

Sync with react.dev @ f3d9794f - #736

Open
react-translations-bot wants to merge 16 commits into
mainfrom
sync-f3d9794f
Open

Sync with react.dev @ f3d9794f#736
react-translations-bot wants to merge 16 commits into
mainfrom
sync-f3d9794f

Conversation

@react-translations-bot

Copy link
Copy Markdown
Collaborator

This PR was automatically generated.

Merge changes from react.dev at f3d9794

The following files have conflicts and may need new translations:

Please fix the conflicts by pushing new commits to this pull request, either by editing the files directly on GitHub or by checking out this branch.

DO NOT SQUASH MERGE THIS PULL REQUEST!

Doing so will "erase" the commits from main and cause them to show up as conflicts the next time we merge.

aurorascharff and others added 16 commits July 20, 2026 15:31
* Resize long og image text

* address feedback
Please accept my changes for React Alicante and CityJS Athens
* Document browser-only rendering

Add the Canary browser API reference, including optional lazy reasons, server bailout reporting, fatal and abort behavior, navigation entries, and onBrowserBailout options for every streaming, resume, and prerender API that supports it.

* Polish browser API docs and add live example

* Document browser with use and Suspense

---------

Co-authored-by: Aurora Scharff <aurora.sofie@gmail.com>
* Clarify browser-only rendering guidance

* Polish browser-only guidance wording

* Use Canary markers in browser guidance

* Present browser as a use resource

* Polish browser usage labels

* Address browser guidance review

* Clarify browser return value is opaque

* Restore alternative wording

* Restore hydration alternative wording

* Focus use introduction on resources

* Note stable browser cleanup
* Pin matching React Canary versions in Sandpack demos

* Use cached Canary build in Sandpack demos
* Improve browser-only rendering example

* Clarify browser-only example action

* Show browser-only fallback on reload
* Add conditional browser query example

* Move browser query hook into its own example file

* Use IndexedDB in conditional browser example

* Clarify conditional browser rendering example

* Polish browser rendering examples

* Bridge conditional browser examples

* Tighten conditional browser example intro

* Use time zone for conditional browser example

* Clarify conditional example transition

* Lead conditional browser docs with time zone example

* Address conditional browser rendering feedback

* update

* Clarify conditional browser control flow

* Clarify conditional data fetching pattern

* Clarify conditional rendering outcomes

* Polish conditional browser examples

* Clarify conditional query rendering

* Align conditional browser guidance
…632)

* Document missing Fizz server rendering options and fix resume references

This adds the `formState`, `importMap`, `onHeaders`, and `maxHeadersLength` options to the `renderToPipeableStream` and `renderToReadableStream` reference pages, documents the object form of `nonce` for separate script and style nonces, and adds `importMap`, `onHeaders`, and `maxHeadersLength` to the `prerender` and `prerenderToNodeStream` pages. All of these options are supported in stable releases but were never documented. The `resumeAndPrerender` entries on the `react-dom/static` index were marked as experimental-only even though they ship in stable releases, so the badge is removed, and the `resumeAndPrerender` intro destructured a `postpone` property that is actually called `postponed`.

The `resumeToPipeableStream` page no longer documents a `signal` option because the Node.js implementation neither types nor reads it, and it now documents the `onAllReady` callback that the implementation does support. The same page referred to `resume` in its intro and Returns section where it meant `resumeToPipeableStream`, and the `react-dom/server` index linked both resume entries to the `renderToPipeableStream` page; they now point at their own pages.

Co-Authored-By: Claude Code (kimi-k3[1m]) <noreply@anthropic.com>

* Document the formState option for hydrateRoot

This adds the `formState` option to the `hydrateRoot` reference. The option carries the form state produced by a Server Function form submission so that `useActionState` with a `permalink` returns the submitted state during hydration instead of the initial state, and it must match the `formState` passed to the server renderer. The option shipped in React 19.0 but was never documented.

---------

Co-authored-by: Claude Code (kimi-k3[1m]) <noreply@anthropic.com>
@vercel

vercel Bot commented Sep 7, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated
tr-legacy-reactjs-org Ignored Ignored Preview Sep 7, 2026 4:17am UTC

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants