Sebastian "Sebbie" Silbermann

> AFAICT, in React 19, act always returns a promise, so it may be best to always await it. It's a fake Promise. Only if you pass in an `async`...

I don't disagree. That's exactly what I'm already working on: https://github.com/testing-library/react-testing-library/pull/1214 It's just that the current `act` doesn't need to be awaited. The Promise it returns for sync callbacks is...

> React does not provide an API to set the priority on a component or suspense boundary for hydration. This means you cannot optimise your application to hydrate part of...

@timdeschryver These are docs for an unreleased feature. Please revert.

> ● Graceful Shutdown › development (next dev) › should shut down child immediately > > expect(received).rejects.toThrow() > > Received promise resolved instead of rejected -- https://github.com/vercel/next.js/actions/runs/9882492580/job/27303701793?pr=67165#step:28:354 Seems like a...

Have you checked why we added this? It used to ensure we always target the same syntax level. Changing it randomly on publish is unsafe since we might produce syntax...

You need to wrap `props.children` in Suspense: ```jsx ``` Since you only have Suspense above `RenderAfterMount`, `RenderAfterMount` will unmount once we suspend thus loosing all state. After the lazy component...

@ematipico Is v3 the version you get when you switch to using the release candidate? I switched to using the release candidate yet the extension is still linting repositories that...

Same as https://github.com/testing-library/react-testing-library/issues/1187 but for fake Node.js timers.