dillon1000/react

Commit

Codemod act -> await act (3/?) (#26336)

Similar to the rationale for `waitFor` (see #26285), we should always
await the result of an `act` call so that microtasks have a chance to
fire.

This only affects the internal `act` that we use in our repo, for now.
In the public `act` API, we don't yet require this; however, we
effectively will for any update that triggers suspense once `use` lands.
So we likely will start warning in an upcoming minor.
Browse files
Changed paths11 files
First-parent comparison
M packages/react-reconciler/src/__tests__/StrictEffectsMode-test.js ModifiedM packages/react-reconciler/src/__tests__/StrictEffectsModeDefaults-test.internal.js ModifiedM packages/react-reconciler/src/__tests__/useEffectEvent-test.js ModifiedM packages/react-reconciler/src/__tests__/useMutableSource-test.internal.js ModifiedM packages/react-reconciler/src/__tests__/useMutableSourceHydration-test.js ModifiedM packages/react-reconciler/src/__tests__/useRef-test.internal.js ModifiedM packages/react-reconciler/src/__tests__/useSyncExternalStore-test.js ModifiedM packages/react-refresh/src/__tests__/ReactFresh-test.js ModifiedM packages/react-refresh/src/__tests__/ReactFreshIntegration-test.js ModifiedM packages/react-server-dom-relay/src/__tests__/ReactFlightDOMRelay-test.internal.js ModifiedM packages/use-subscription/src/__tests__/useSubscription-test.js Modified
Patch

Files changed

Rendering syntax-highlighted changes…