Alex Krolick

This page should go under the ecosystem section. It's where all of the libraries that aren't framework adapters go.

https://jestjs.io/docs/configuration#testenvironment-string One approach could be to use a custom environment that creates a new JSDOM global in `handleTestEvent`. This wouldn't just be useful for concurrent tests, it would also isolate...

We can do both. Demographically, Discord doesn't reach/resonate with everyone.

Good idea. The Nodejs docs do that.

yeah, wrangling references to nodes like that is how you end up with wrapper.update() in Enzyme

Thanks for the PR @ab18556, it's a good start. I think at least establishing an ecosystem page like this one would be enough to merge: https://github.com/alexkrolick/testing-library-docs/blob/master/docs/ecosystem-user-event.md

Ok, moving it all into the ecosystem page sounds good, too.

It definitely fits in the ecosystem section, other things like native-testing-library or jest-dom don't depend on any core libs either

I recall this was a point of contention with ReactRouter regarding the recommended approach, because you can't interop with window.location and other APIs that real apps use in conjunction with...

Previous discussion: https://github.com/ReactTraining/react-router/pull/7169#issuecomment-597397021