-
-
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
Path resolution issues with Jest@20 #3542
Comments
This is probably related to #3541 |
This should fix it: #3538 (except for |
Thanks @thymikee! Does that also cover the |
Hm, not sure about that, we need to test nested configs more thoroughly after recent rewrite. |
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. |
Do you want to request a feature or report a bug?
bug
What is the current behavior?
I'm unsure what's happened, but maybe a diff will help reveal what's going on.
Here's how I had to change things when upgrading from a working Jest@19 setup to an almost working setup with Jest@20
I think this is important to note: My config is located in
<rootDir>/tests/jest.config.client.json
and my root is in<rootDir>/public/js
.Really sorry I was unable to try the alpha out on my project :-(
With these changes, Jest starts running the tests, but it appears it's not transpiling things properly.
The text was updated successfully, but these errors were encountered: