-
Notifications
You must be signed in to change notification settings - Fork 391
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JestMatchersShape<Matchers<void, HTMLElement>, Matchers<Promise<void>, HTMLElement>> doesn't has toBeVisible / toBeInDocument attributes #178
Comments
Sorry I can't reproduce the error a moment later. It looks so strange, I tried reloading vscode window, restarting vscode and waited for a long time, the error always there... So I went to do other things, then suddenly found the error disappeared and the definition shown. So it works fine now, although I have done nothing to fix it. I should close the issue now. |
I have a similar error while running tests and using vscode. I have noticed that based on |
@reinismu we'd need a sample repo where this can be reproduced. |
I've actually run into this same problem in my code. Jest will run the tests properly after a fresh reboot; when I revise the I'll have to create a sample repo to try and reproduce this. |
I've run into this issue with vscode and running tests in watch mode. After doing a |
I had the same issue and fixed it by installing @types/testing-library__jest-dom, hope this helps someone |
I run into this issue too, just init the project with CRA. And fixed it by add @types/testing-library__jest-dom package. |
@testing-library/jest-dom
version: 4.2.4node
version: 10.16.0npm
(oryarn
) version: yarn v1.19.1Relevant code or config:
What you did:
I configure the @testing-library/jest-dom/extend-expect following README.md Usage - 1
What happened:
The typescript definition doesn't work:
In English, the error means
JestMatchersShape<Matchers<void, HTMLElement>, Matchers<Promise<void>, HTMLElement>> doesn't has toBeVisible / toBeInDocument attributes
Related issue:
It seems pointed out before, but the solution doesn't work
#11 (comment)
The text was updated successfully, but these errors were encountered: