Skip to content

Clarify that Transition Actions can be asynchronous - #8696

Open
yotatameguchi-boop wants to merge 1 commit into
reactjs:mainfrom
yotatameguchi-boop:docs/clarify-async-transition-actions
Open

yotatameguchi-boop wants to merge 1 commit into
reactjs:mainfrom
yotatameguchi-boop:docs/clarify-async-transition-actions

Conversation

@yotatameguchi-boop

Copy link
Copy Markdown

The troubleshooting section says that the function passed to startTransition must be synchronous, even though the page documents async Actions and demonstrates startTransition(async () => { ... }).

Replace that restriction with the constraint demonstrated by the adjacent example: updates in a later setTimeout callback are not marked as Transitions. Explicitly acknowledge that Actions can be asynchronous. The following section continues to explain the separate requirement to wrap state updates after await in another startTransition.

Validation:

  • Confirmed consistency with the action parameter description and the existing async Action examples.
  • git diff --check passes.
  • Verified that code blocks, links, heading anchors, and line count are unchanged.

This is a prose-only change. The site build and browser preview were not run.

@github-actions

Copy link
Copy Markdown

Size changes

Details

📦 Next.js Bundle Analysis for react-dev

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

This branch was successfully deployed

1 active deployment
Preview — 1b69e165 Deployed Oct 15, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant