Repository navigation
Sync with react.dev @ f5fa1e82 - #265
Merged
Merged
Conversation
…Effect reference (#8707) * Fix broken React Router link in "Synchronizing with Effects" * Fix broken React Router link in useEffect reference
… Conf Japan 2027 section (#8700) * Update conferences: move concluded Sep 2026 events to Past, fix React Conf Japan 2027 section * Update conferences: move concluded CityJS Athens 2026 to Past section * Update conferences: move concluded React Advanced London 2026 to Past section
Twitter, Threads, and Bluesky links already included the member's
name in their aria-label, but GitHub and personal-site links used
generic labels ("GitHub Profile", "Personal Site") with no name —
inconsistent and confusing for screen reader users scanning the
team page. Standardize all five link types to include the member's
name, and mark their icons aria-hidden since the link's accessible
name already conveys the same information.
Fixes #8552
Co-authored-by: Claude <noreply@anthropic.com>
…age (#8571)" (#8729) This reverts commit 6be2e2a.
Co-authored-by: Iitian001 <Iitian001@users.noreply.github.com>
…#8538) * Fix Server Functions documentation examples * Fix code snippet highlights Corrected the index of 'submitAction' in the code snippet. * Clarify wording * Update section titles for clarity * Polish Server Functions examples: consistent headings, reset wording, transition comment - Convert the remaining two Usage headings to gerund form to match the rest of the page and react.dev convention (anchors unchanged) - Reset wording: "succeeds" + "the form's uncontrolled fields" (aligns with #8512) - Comment the startTransition-after-await; bump CodeStep line accordingly Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * Polish Server Functions examples * Fix Server Functions code highlight --------- Co-authored-by: Aurora Scharff <aurora.sofie@gmail.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* Enhance form documentation for form default reset behavior * Reorder sections for better progressive disclosure of ideas * fix typos in form.md * Normalize MDN links in form.md * Standardized all Usage headings in form.md to imperative form * add useOptimistic reference * Standardize section headings in form.md to imperative form * revert 'action' prop change * Enhance form submission documentation by clarifying the use of the `action` prop and its behavior: - including the handling of `FormData`, - the necessity of `name` attributes, - the advantages of using a function over a URL. - removed redundant information about `e.preventDefault()` for the `action` prop. * clean up Handling form submission with an action prop * clean up preserving form values after submission * update code example for Handling multiple submission types * Clean up code example for Handling multiple submission types * update form documentation with more examples of keeping form values after submission * add useFormStatus to benefits of using Action * Move reset form section to the bottom of the page and update examples * updates based on pr feedback * Enhance form documentation by clarifying the `action` and `method` props, including details on handling form submissions with functions and the implications of using `formAction`. Update examples and caveats for better understanding of form behavior in React. * small cleanups * Refine form Action documentation * update Preserving form values after an Action section based on feedback * update on onSubmit vs action prop note * Enhance form documentation by expanding on the use of Server Functions in the `action` prop, including detailed examples for passing extra data and handling form submissions. Clarify the behavior of form elements and their interaction with `FormData`. * fixing onSubmit link and code example clean up * remove unneeded hidden items * Polish form documentation wording * Restore Transition link in form docs * Clarify form value preservation examples and guidance --------- Co-authored-by: Aurora Scharff <aurora.sofie@gmail.com>
… (#8653)
requestUsername is passed to useActionState but declared as
requestUsername(formData). useActionState calls the action with the
previous state as the first argument, so formData ends up null and
formData.get('username') throws. The useActionState reference already
covers this under "My Action cannot read form data".
Also drop a stray semicolon in the LikeButton example, where it sits in
the fragment's children and renders as text, and remove a duplicated
word in the RSC banner so it matches use-client.md.
…) (no AI or LLM used) (#8702) Thanks to the React team for great documentation! As a way to give back, I would like to share some simple typo fixes (any other type of content issues found will be fixed in separate commits): - On https://react.dev/reference/react/useActionState (archived as is at https://web.archive.org/web/20261022181815/https://react.dev/reference/react/useActionState ) "quanitiy" should be "quantity". - On https://react.dev/reference/react/useContext (archived as is at https://web.archive.org/web/20261022181858/https://react.dev/reference/react/useContext ) "mistakingly" should be removed (the sentence already ends in "by mistake", and "mistakenly" would seem to be the intended word if that had not been the case) - On https://react.dev/reference/react/experimental_taintUniqueValue (archived as is at https://web.archive.org/web/20261022181913/https://react.dev/reference/react/experimental_taintUniqueValue ) "untained" should be "untainted" - On https://react.dev/reference/react-dom/flushSync (archived as is at https://web.archive.org/web/20261022184601/https://react.dev/reference/react-dom/flushSync ) "syncronous" should be "synchronous" - On https://react.dev/reference/react-dom/client/createRoot (archived as is at https://web.archive.org/web/20261022185916/https://react.dev/reference/react-dom/client/createRoot ) "specfied" should be "specified" - On https://react.dev/reference/react-dom/client/hydrateRoot (archived as is at https://web.archive.org/web/20261022190025/https://react.dev/reference/react-dom/client/hydrateRoot ) "specfied" should be "specified" - On https://react.dev/reference/react-dom/server/resume (archived as is at https://web.archive.org/web/20261022190141/https://react.dev/reference/react-dom/server/resume ) "immediated" should be "immediately" - https://react.dev/reference/dev-tools/react-performance-tracks (archived as is at https://web.archive.org/web/20261022190242/https://react.dev/reference/dev-tools/react-performance-tracks ) "addititional" should be "additional" - https://react.dev/reference/eslint-plugin-react-hooks/lints/use-memo (archived as is at https://web.archive.org/web/20261022190325/https://react.dev/reference/eslint-plugin-react-hooks/lints/use-memo ) "sychronizes" should be "synchronizes" - https://react.dev/versions (archived as is at https://web.archive.org/web/20261022190519/https://react.dev/versions ) "Specificaion" should be "Specification" - https://react.dev/reference/react/StrictMode (archived as is at https://web.archive.org/web/20261022190822/https://react.dev/reference/react/StrictMode ) "inital" should be "initial"
* Update conference listings for 2026 * update typo for cityjs singapore 2026 website * fix header typo for react india * remove duplicates from past 2025 conference * Update dates for React miami and react summit 2026 --------- Co-authored-by: Aurora Scharff <aurora.sofie@gmail.com>
* docs: clarify that Transition Actions can be asynchronous * Keep async Action clarification focused * Clarify sync and async Transition callbacks --------- Co-authored-by: Aurora Scharff <aurora.sofie@gmail.com>
* docs: explain useFormStatus with custom form actions Closes #8682. Document when `useFormStatus().pending` is set for a `preventDefault()` submit handler that starts a Transition in the same event, and add a runnable example for a custom form action. The example also notes that this pattern does not reset the form automatically. Validation: `yarn check-all` and `git diff --check` pass locally. The initial draft was prepared with AI assistance and reviewed against the React DOM tests and issue details. * Polish useFormStatus onSubmit documentation * Clarify pending status and link form reset guidance * Shorten pending definition and link onSubmit guidance * Link form submission and Transition references * Make form pending-state headings parallel --------- Co-authored-by: Aurora Scharff <aurora.sofie@gmail.com>
Four links in Learn docs were missing the leading slash and would resolve to 404 paths. Every other internal link in the repo uses absolute paths.
Fixes #6933 The Server Components docs page had inconsistent handling of the note variable across 3 code examples. All examples now consistently treat note as an object with .authorId, .id, and .content properties.
Remove accidental repeated words in three reference pages: - createRoot: 'can can' -> 'can' - resumeAndPrerenderToNodeStream: 'a a' -> 'a' - react-performance-tracks: 'the the' -> 'the' Co-authored-by: eknathdj <eknathdj@users.noreply.github.com>
…#8483) The ChatRoom.js sandpack in the "Fix a connection switch" challenge imports useState but only uses useEffect. Remove the unused import to avoid confusing learners. Fixes #8231
Removed unused import of useState from React.
- 'an custom' -> 'a custom' in components/index.md (consonant sound) - 'a object' -> 'an object' in taintUniqueValue.md (vowel sound)
…(#8667) * Explain that the useState setter triggers a re-render in Quick Start * Explain re-render behavior before naming it --------- Co-authored-by: Dextheking1 <Dextheking1@users.noreply.github.com> Co-authored-by: Aurora Scharff <aurora.sofie@gmail.com>
* Fix act() dispatch example using button before it is defined The event example called button.dispatchEvent before const button was declared, which would throw at runtime. Also drop it.only from the docs snippet. * Highlight the full act event-dispatch block --------- Co-authored-by: Aurora Scharff <aurora.sofie@gmail.com>
…nsition (#8642) * Remove redundant async in useTransition documentation * Fix typo in useActionState hook documentation
* Clarify ref callback cleanup vs null behavior * docs: incorporate review feedback on ref callback cleanup
Co-authored-by: sunmozong <sunmozong@kuaishou.com>
Co-authored-by: Ricky <rickhanlonii@gmail.com>
Fixes reactjs/react.dev#8375 The tutorial incorrectly used 'argument' when referring to the function parameter in the handleClick function declaration. In JavaScript: - Parameter is the variable in the function declaration - Argument is the actual value passed when calling the function This change improves accuracy and helps learners understand the distinction between these two important programming concepts.
* Update lifecycle-of-reactive-effects.md * Remove useEffect from solution as well --------- Co-authored-by: Jaem <91131509+DarkChocoJaem@users.noreply.github.com>
Size changesDetails📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖 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 branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was automatically generated.
Merge changes from react.dev at f5fa1e8
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.