You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* You must wrap any state updates after any async requests in another `startTransition` to mark them as Transitions. This is a known limitation that we will fix in the future (see [Troubleshooting](/reference/react/useTransition#react-doesnt-treat-my-state-update-after-await-as-a-transition)).
67
66
@@ -102,11 +101,8 @@ With a Transition, your UI stays responsive in the middle of a re-render. For ex
102
101
103
102
The standalone `startTransition` and the function returned by
104
103
[`useTransition`](/reference/react/useTransition) both mark state updates as
105
-
Transitions. The standalone function does not provide the `isPending` flag and
106
-
is not associated with a component. If the function passed to it throws an
107
-
error or returns a rejected Promise, React reports the error as uncaught instead
108
-
of allowing an Error Boundary to handle it. Unlike `useTransition`, the
109
-
standalone `startTransition` is not a Hook and can be called outside components.
104
+
Transitions. Unlike `useTransition`, the standalone function does not provide
105
+
the `isPending` flag. It is not a Hook, so you can call it outside components.
110
106
[See Caveats.](#caveats)
111
107
112
108
[Learn about Transitions and see examples on the `useTransition` page.](/reference/react/useTransition)
0 commit comments