-
Notifications
You must be signed in to change notification settings - Fork 508
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
ts-jest cache issue #919
Comments
Possibly same as #908? |
It was definately the caching. This fixed it. So this makes it a dupe of the above. Closing. |
Yea TSDX does not read TSDX also dogfoods You may have misread the test output too, because it doesn't show it reading a file from
It does show the output for that file to be from a different file though, which, yes does sound like an upstream cache issue.
Specifically, that output is not from Jest, but from
#908 is also a cache problem, but it's quite a different one. That one is a But in any case, this issue is upstream in |
Thanks for the detailed response. I disabled caching for ts-jest, the problem has vanished. |
Current Behavior
Jest runs tests in the node_modules directory (maybe), or it's somehow caching old ts files somewhere?
Expected behavior
Tests not to be run in the node_modules directory
Suggested solution(s)
I'm not actually sure what's causing this, so it's hard to say. The jest config looks ok to me
Additional context
This is a pretty new project, so it's not customised. I also had a play with manually adding node_modules to the file ignore list in the jest config, just to check that the default was working as expected, and that didn't seem to make a difference.
Your environment
The text was updated successfully, but these errors were encountered: