Sync with react.dev @ a8790ca8 #922
Conversation
* Cleanup old ga-lite tag and refactor GA4 * cleanup * cleanup2
* Add Error Boundary to useTransition docs * add Error Boundary to useTransition * Use Canary * Add Error Boundary to useTransition API docs * Update src/components/MDX/Sandpack/Preview.tsx Co-authored-by: Jan Kassens <[email protected]> * Update src/content/reference/react/useTransition.md Co-authored-by: Luna <[email protected]> * Update src/content/reference/react/useTransition.md Co-authored-by: Luna <[email protected]> * Add Error Boundary to useTransition docs * add Error Boundary to useTransition * Use Canary * Add Error Boundary to useTransition API docs * Update src/components/MDX/Sandpack/Preview.tsx Co-authored-by: Jan Kassens <[email protected]> * Update src/content/reference/react/useTransition.md Co-authored-by: Luna <[email protected]> * Update src/content/reference/react/useTransition.md Co-authored-by: Luna <[email protected]> * Address comments and update usage example * Address comments and update usage example * Update src/content/reference/react/useTransition.md Co-authored-by: Luna <[email protected]> --------- Co-authored-by: Jan Kassens <[email protected]> Co-authored-by: Luna <[email protected]>
* Warn about low entropy in taintUniqueValue.md * Update src/content/reference/react/experimental_taintUniqueValue.md Co-authored-by: Jan Kassens <[email protected]> --------- Co-authored-by: Jan Kassens <[email protected]>
Add useFormState reference
* Add useFormState reference * Matt's suggestions for useFormState reference * Incorporated PR feedback for useFormState
Co-authored-by: Nikhil Gupta <[email protected]>
Co-authored-by: Luna <[email protected]>
* Add useOptimistic API reference documentation * Fix title * Add working exmaple from form and updadd parameters * Add updates to useOptimistic * Add updates to useOptimistic * Add updates to useOptimistic --------- Co-authored-by: Matt Carroll <[email protected]>
Google uses this on many of our API doc pages and it's not a good snippet. Only put this on the homepage but leave the og:description and twitter:description.
* Adds landing page for reference section.) * Updated hyperlinks. * Fixes Legacy APIs link. * Removes canary image from heading.
Co-authored-by: Sophie Alpert <[email protected]> Co-authored-by: Luna Wei <[email protected]>
Co-authored-by: Soichiro Miki <[email protected]> Co-authored-by: David McCabe <[email protected]> Co-authored-by: Luna Wei <[email protected]>
* Edits for new "use client" content * Apply suggestions from code review Co-authored-by: Luna <[email protected]> --------- Co-authored-by: Luna <[email protected]>
Size changes📦 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! Three 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 a8790ca
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.