Sebastian "Sebbie" Silbermann

The solution here is a custom entrypoint instead of a configuration. The current ones are more subject to being really global but a wrapper really isn't. It's highly subjective to...

Can you give an example of a failure (ideally a complete, minimal, cloneable repro) that we should auto-fix?

Looks like you're using a `.ts` file not a `.tsx` file. Can you provide a cloneable repro or, ideally, a [TypeScript playground](https://www.typescriptlang.org/play)?

It's likely an editor misconfiguration. It parses the file as ts not tsx hence the "Parsing error: '>' expected".

There's a reason why we should do this now and a React specific reason that why we may need to do it in the future. For now consider this test:...

We already don't let people assert between what was committed from render and what was committed from `useEffect`. If that is what we want, we need to go back and...

I have a bit of time start of October where I want to revisit this. So testing how good codemod coverage is. Testing react-dom and react-native tests. Checking if we...

Yeah this is one of the scenarios we'd like to address with https://github.com/testing-library/react-testing-library/pull/1214 but it needs some additional time. If you're blocked by this, you can always `render().unmount()` or `cleaup()`...

We need to move `@types/react-dom` to (optional) peer dependencies. Though this is technically a breaking change even though it rarely is practically. I'll read up again on prior discussions. In...

It's about different dependencies so I wouldn't consider this a duplicate issue.