Sebastian "Sebbie" Silbermann

Fixed in https://github.com/testing-library/react-testing-library/pull/1137 Released in `@[email protected]`

Once TypeScript 5.1 is out (scheduled for 30th of May) we'll land https://github.com/DefinitelyTyped/DefinitelyTyped/pull/65135 which fixes this issue.

`initialProps` is for the hook, not the component. We should change the naming to avoid confusion. testing-library/react-hooks passed `initialProps` to both which is also confusing because it's harder to reason...

Closing in favor of https://github.com/facebook/react/issues/27479

Note the ```jsx render(ui, { wrapper: () => ui, ``` This means that your wrapper will always render the initial element not the element given to `rerender`. Remember that `wrapper`...

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....

What Node.js version are you using? > As I mentioned, the promise does actually get handled with the call to await result; That's not where the error message is pointing...

Can you create a repro that's as minimal as possible? Preferably no TypeScript and no `user-event` (can use `fireEvent.click` instead).

CI should be green with https://github.com/testing-library/dom-testing-library/pull/1262. We'll continue to need the overrides otherwise we'll encounter this issue again.

@MatanBobi Started the release train but then real life happened so I don't think anybody is actively driving this.