Sync with react.dev @ 91614a51 #79
Conversation
* React v19 blog update * re-add sebbie's install updates Co-authored-by: Sebastian Silbermann <[email protected]> --------- Co-authored-by: Sebastian Silbermann <[email protected]>
* Convert "Canary" callouts to "React 19 beta" (#6811) * Convert "Canary" callouts to "React 19 beta" * Starting in * Bump version string * Bump deploy * Bump deploy * Bump deploy * [19] Remove <NextMajor> callouts (#6844) * Remove <NextMajor> callouts * rm if(node) * Delete removed APIs from 19 docs (#6845) * Add information about ref handling in strict mode (#6777) * Add information about DOM ref handling in strict mode * switch order of ref object / ref callback in strictmode doc * use 'refs to components' terminology instead of 'DOM refs' * update references to canary/r19 * Expand usage example and remove badges --------- Co-authored-by: Rick Hanlon <[email protected]> * [19] s/"Server Action"/"Server Function" (#7180) * [19] s/Server Action/Server Function * Revert /blog and change redirect * Add note * Tweak note * [v19] Update sandboxes to 19 RC (#7196) * Update transition docs for React 19 (#6837) * Add async transitions to React 19 docs * Updates from feedback * tweaks * grammar * Add startTranstion API * Apply suggestions from code review Co-authored-by: Noah Lemen <[email protected]> * Updated * capitalization * grammar --------- Co-authored-by: Noah Lemen <[email protected]> * [19] Add docs for prerender APIs (#7320) * Add prerender APIs * fix code blocks --------- Co-authored-by: Noah Lemen <[email protected]>
* fix links * Update startTransition.md * Update startTransition.md * Update startTransition.md * Update startTransition.md
"use-server" docs Server Functions href fixed.
* Fix stylesheet precedence example * Update link.md --------- Co-authored-by: dan <[email protected]>
Co-authored-by: Josue Navas <[email protected]>
docs: fixed typo act md counter fn grammar error
… appropriate section (#7354)
the “Dealing with rejected Promises” codesandbox example depends on react-error-boundary, but doesn’t specify it as a dependency, so the code example is broken
In the section "Importing Server Functions from Client Components" updated "createNoteAction" to "createNote" to match the function name in the example
Added React Universe Conf 2025 to the list of conferences
Co-authored-by: Sebastian Markbåge <[email protected]> Co-authored-by: Rick Hanlon <[email protected]> Co-authored-by: eps1lon <[email protected]>
* Update Conferences Lists for 2025 * fix typo * Fix typo
…blog posts (#7431)
* Update conferences.md for CityJS Athens and London Events Dear people, I would really appreciate if you include our community events on your website. It might not be titled as React conferences but it does have a lot of React on it! Thank you it is very much appreciated. * Update conferences.md Removed spaces as requested.
Reuses the main repo's workflow to label if a PR is opened by a core team member.
* update version to latest + move folders around * getting home page working * make the mdx setup work * bypass mdxname * split out mdx components * re-add meta mdx logic * replace mdxName usage * fix code blocks * fix max width * convert mdx post processing to actual plugins * fix tailwind * fix incorrect iframe props * cleanup mdx dic * make it actually build * align fonts * fix uwu script * fix search * remove _app * make it actually build * replace next-watch-remote with custom setup * clean up logs + clean up inline scripts * add rss handler * remove rss generation * remove rss generation * support MDX components for TOC * clean up log + bump cache * fix toc * add back translations + add new overlay * use MDX link instead of Next.js links for translation * fix analytics * add myself to the contributors * fix blinking sidebar * avoid rendering toc on the client * plugin metadata * simplify metadata * fix title * clean up metadata * add back error decoder * Update src/content/learn/index.md --------- Co-authored-by: Ricky <[email protected]>
This reverts commit 0eb0f88.
* Fix Vite link * Fix additional vitejs.dev URLs to use vite.dev
Size changes📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖
|
| Page | Size (compressed) |
|---|---|
global |
110.44 KB (🟡 +6.14 KB) |
Details
The 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 <script> tag are not accounted for in this analysis
If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!
Six Pages Changed Size
The following pages changed size from the code in this PR compared to its base branch:
| Page | Size (compressed) | First Load |
|---|---|---|
/404 |
127.1 KB (🔴 +22.33 KB) |
237.54 KB |
/500 |
127.11 KB (🔴 +22.35 KB) |
237.55 KB |
/[[...markdownPath]] |
128.97 KB (🔴 +22.35 KB) |
239.4 KB |
/_error |
190 B (🟡 +9 B) |
110.62 KB |
/errors |
127.38 KB (🔴 +22.41 KB) |
237.82 KB |
/errors/[errorCode] |
127.36 KB (🔴 +22.4 KB) |
237.79 KB |
Details
Only 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 next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.
Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis
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 91614a5
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.