Sebastian "Sebbie" Silbermann

Seems to work just fine in the CodeSandbox: https://github.com/user-attachments/assets/7e812ced-ed76-4f8b-b466-793d60554468 Maybe there's something mocking timers in your Vitest suite? React Testing Library currently doesn't integrate with fake timers in Vitest.

It doesn't look like this bug report has enough info for one of us to reproduce it. Please provide a CodeSandbox (https://react.new), or a link to a repository on GitHub....

This is intended behavior. React will batch state updates if possible. `useEffect` only runs when React commits, not when React renders.

`React.cache` only works in the `react-server` environment which React Testing Library doesn't support yet. A version of RTL for React Server Components needs design first: https://github.com/testing-library/react-testing-library/issues/1209

You shouldn't mock `React.cache`. React Testing Library has no support for React Server Components at the moment so you shouldn't mock away RSC specific APIs. The test results you'd receive...

Might be interesting to revisit pointer capture again. That's what we're effectively pollyfilling here. But I didn't pursue back then due to browser bugs/lack of support. So depending on your...

We fixed some scenarios where this could occur in React DevTools 7.0. If this issue still persists, please open a new issue.

Can you try this without an uncached Promise e.g. by moving the Promise creation outside of the render of `App`?

Ready to merge

I'm looking for the Job URL e.g. https://github.com/vercel/next.js/actions/runs/12000501567/job/33449700959. If we'd be able to configure this, we'd have the choice of actually querying the workflow ID from GH Apis. Since it's...