Sync with react.dev @ 8c68ae8d - #984
react-translations-bot wants to merge 14 commits into
Conversation
* 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>
* Validate inline code highlights in docs * Match MDX code highlight metadata parsing
* Clarify standalone startTransition error handling * Polish startTransition error handling docs * Describe startTransition differences neutrally * Clarify startTransition callback wording * Remove repeated startTransition caveat * Preserve existing startTransition guidance * Preserve useTransition error guidance * Update src/content/reference/react/useTransition.md Co-authored-by: Sebastian "Sebbie" Silbermann <silbermann.sebastian@gmail.com> * Clarify standalone startTransition error reporting --------- Co-authored-by: Sebastian "Sebbie" Silbermann <silbermann.sebastian@gmail.com>
* Update browser.md * Update browser.md
* Add React Advanced London 2026 and React Summit US 2026 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * Retrigger CI * Add React Day Berlin 2026, React Summit Asia 2027 and React Summit 2027 * Fix React Summit Asia 2027 dates * Add LinkedIn links for React Summit and React Day Berlin * Remove extra blank line between conference entries --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
* Document React-specific img behavior * Explain empty image source caveat
…673) Both became stable in React 19.3 and both have reference pages and sidebar entries, but neither is listed on its overview page: - `<ViewTransition>` is missing from Built-in React Components, which already lists its 19.3 sibling `<Activity>`. - `addTransitionType` is missing from Built-in React APIs, which already lists `cache`, `cacheSignal` and `captureOwnerStack`. CONTRIBUTING.md says the API Reference "is intended to be exhaustive", so a reader browsing either overview page currently can't discover either API. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
Size changesDetails📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖 🎉 Global Bundle Size Decreased
DetailsThe global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster. Any third party scripts you have added directly to your app using the If you want further insight into what is behind the changes, give @next/bundle-analyzer a try! Five Pages Changed SizeThe following pages changed size from the code in this PR compared to its base branch:
DetailsOnly the gzipped size is provided here based on an expert tip. First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If Any third party scripts you have added directly to your app using the Next to the size is how much the size has increased or decreased compared with the base branch of this PR. If this percentage has increased by 10% or more, there will be a red status indicator applied, indicating that special attention should be given to this. |
This PR was automatically generated.
Merge changes from react.dev at 8c68ae8
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.