Describe the feature you'd like:

Being new to testing-library, it all is a bit overwhelming. The long list of matchers jest-dom introduces, also makes it harder to start out.

Suggested implementation:

Group the matchers in the documentation over some headings, e.g. “Checking element existence”, “Checking forms”, “Checking element state”.

Describe alternatives you've cons

So, I added this feature:

- await waitForElementToBeRemoved(() => screen.getByText('foo'))

+ const element = screen.getByText('foo')
+ await waitForElementToBeRemoved(element)

Both work, but the first I think is easier most of the time.

But I just learned that in React applications (and likely other frameworks) the DOM nodes aren't always removed, rather they're updated.

Hello, I tried to include this hook in my RN app and when I wrapp my AppContainer in the ModelProvider it throws this error.
My current dependencies are:

"dependencies": {
    "expo": "^34.0.1",
    "expo-font": "^6.0.1",
    "native-base": "^2.13.4",
    "prop-types": "^15.7.2",
    "react": "16.8.3",
    "react-dom": "^16.8.6",
    "react-modal-hook": "^2.0.0",
    "react-native

I've stopped creating domains for projects that might not get traction. Instead I am now hosting most of my projects under a subdomain or subfolder of my main domain. Hence, this Dashboard project currently lives under dashboard.darekkay.com.

However, if this project becomes more popular, it should get a proper name and an own domain. So far, I didn't find a n

Add react router v5 to the boilerplate. Easy to set up and configurable routes should be the first priority.