-
Notifications
You must be signed in to change notification settings - Fork 267
Sync with react.dev @ 97489434 #647
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
Conversation
* Remove pitfall and update Next link * Fix other beta link --------- Co-authored-by: Luna Wei <luwe@fb.com>
Co-authored-by: Luna <lunaleaps@gmail.com>
* Update react-labs-what-we-have-been-working-on-june-2022.md * Update react-labs-what-we-have-been-working-on-june-2022.md
…5836) * Update referencing-values-with-refs.md * Update src/content/learn/referencing-values-with-refs.md
Maybe it's debatable whether we want to link to canary APIs in other pages but I feel like here it's more useful than not.
Co-authored-by: Matt Carroll <mattca@meta.com>
* Explain limitations of useSyncExternalStore with concurrency Doesn't seem like we have this noted anywhere. * Pull out example to code block
* Upgrade react-collapsed * 4.0.4 --------- Co-authored-by: Rogin Farrer <rfarrer@wayfair.com>
Added new meetup in Saskatoon - SK
Co-authored-by: Luna Wei <luwe@fb.com>
* fix: add a missing import statement in useFormStatus.md * Update src/content/reference/react-dom/hooks/useFormStatus.md Co-authored-by: Ahmed Abdelbaset <A7med3bdulBaset@gmail.com> --------- Co-authored-by: Ahmed Abdelbaset <A7med3bdulBaset@gmail.com>
Co-authored-by: Luna Wei <luwe@fb.com>
* Cleanup old ga-lite tag and refactor GA4 * cleanup * cleanup2
Co-authored-by: Sebastian Silbermann <silbermann.sebastian@gmail.com> Co-authored-by: Allison Strandberg <55810428+allison-strandberg@users.noreply.github.com>
This example contains a list of person objects, but only the first 3 have id properties. This appears to be a mistake; in the next use of the list all 5 person objects have this property, but it is not changed as part of an instructive exercise. This change makes the final two with objects consistent with the remainder of the list.
`an text area` -> `a text area` `an discussion` -> `a discussion`
…6728) Signed-off-by: Faridul Islam <foridpathan45@gmail.com>
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
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! New Pages AddedThe following pages were added to the bundle from the code in this PR:
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 9748943
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.