Skip to content
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

Sync with react.dev @ fc296034 #82

Open
wants to merge 200 commits into
base: main
Choose a base branch
from
Open

Conversation

react-translations-bot
Copy link
Collaborator

This PR was automatically generated.

Merge changes from react.dev at fc29603

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.

rickhanlonii and others added 30 commits May 20, 2024 10:53
Co-authored-by: OH HYUN KEUN <[email protected]>
This upstreams some of the [introduction
post](reactwg/react-compiler#5) into the
docs since this knowledge is quite fundamental to understanding the
compiler, and it's confusing to not have it linked in the canonical
source for the docs. It also adds more information about
[debugging](reactwg/react-compiler#7) and
reorganizes a few sections to make things clearer

ghstack-source-id: ef32fc723722eb5119529abcc572dd2bcf2b1cab
Pull Request resolved: reactjs/react.dev#6895
* Add React Conf 2024 Recap post

* Spelling and links

* Apply suggestions from code review

Co-authored-by: lauren <[email protected]>

* Edits

* Edits

* better link

* Update date

* Update date and nits

* feedback

---------

Co-authored-by: lauren <[email protected]>
* Add codemods to upgrade guide

* Update src/content/blog/2024/04/25/react-19-upgrade-guide.md

Co-authored-by: Ahmed Abdelbaset <[email protected]>

* Add benefits

---------

Co-authored-by: Ahmed Abdelbaset <[email protected]>
The docs for stylesheet precedence incorrectly state that there is an enumerated set of valid precedences. This is incorrect. The precedence value can be anything and React infers the hierarchy from the order in which it discovers precedences
* FIX: Typo in useEffect.md caveats

* Fix another typo
* Add act documentation

* Update structure based on feedback

* Add usage examples and async act

---------

Co-authored-by: Rick Hanlon <[email protected]>
Fix very minor typo
Added missing comma to the codesample.
Expo now has its own instructions for enabling the compiler.
akiran and others added 29 commits February 10, 2025 15:57
* Blog and docs: Sunsetting Create React App

* fix link

* tweaks

* fix markdown

* clarity + thanks
…te React App (Depreacted) page section (#7612)
* fix(docs): webpack branding states it should be lower case

* chore: fix more occurrences

---------

Co-authored-by: Strek <[email protected]>
* [Blog + Docs] Updates from feedback

* Merge in changes from #7618

Co-authored-by: Mark Erikson <[email protected]>

* Say the words "Vite", "Parcel", and "Rsbuild"

* Tweaks from feedback

* re-apply #7615

* merge in #7622

Co-authored-by: elitalpa <[email protected]>

---------

Co-authored-by: Mark Erikson <[email protected]>
Co-authored-by: elitalpa <[email protected]>
* Remove starting react project from setup page

* Fix typo
fix 18.3.0 release changelog link
* Update nextjs link with the latest URL

The previous link redirected users to a 404 page.

* Update src/content/reference/react/useDeferredValue.md

---------

Co-authored-by: Ricky <[email protected]>
* Update input.md

Fix typo about input

* Update src/content/reference/react-dom/components/input.md

---------

Co-authored-by: Ricky <[email protected]>
* clarify alert message behavior in issue #7494

Reworded the explanation regarding the alert message in the documentation to better describe its behavior. The alert shows the previously entered name, with an initial value set to an empty string.

* Update src/content/learn/state-a-components-memory.md

* Update src/content/learn/state-a-components-memory.md

---------

Co-authored-by: Ricky <[email protected]>
* Fix broken header link

* Update sunsetting-create-react-app.md
…r <style> when using the `precedence` property (#7643)
This is the exact same fix as #6422 as the example is duplicated between the useOptimistic and <form> pages.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment