-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
"Module * in the testRunner option was not found" when using "resolver": "browser-resolve" #10297
Comments
+1 Getting exactly the same issue. |
I ran |
I found that somehow, the
And I had to install jest-circus, just like Sean said:
|
Did anyone solve it without installing |
Try to remove |
I just recently created a new React app using I had to change the Jest |
thank you, it's working now |
I had the same issue (hardcoded path). I just did an eject, probably it was because of that. |
I was having the exact same issue when using Docker, this fixed it. Thanks! |
Same here, did an eject earlier which added the absolute path that broke everything. |
Default export if Hard coded |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
π Bug Report
When setting
"resolver": "browser-resolve",
option, jest shows the following error:<PATH>/node_modules/jest-jasmine2/build/index.js
does exist.To Reproduce
package.json
:test.test.js
:Tried also installing
jest-circus
and adding:and I'm getting
I guess it's related to recent deprecation of
browser
: https://github.com/facebook/jest/pull/9943/filesWhen I use the deprecated
browser
field, I'm getting a deprecation warning, but tests pass:Expected behavior
No errors.
Link to repl or repo (highly encouraged)
REPL: https://repl.it/repls/HumongousSpottedMp3
envinfo
The text was updated successfully, but these errors were encountered: