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
[Bug]: Not starting with Yarn #13796
Comments
I also see the behavior if I unplug jest from PnP with |
This seems to work on a different Windows machine I have. The main difference between the 2 machines is that the one that its working on has only 1 drive (C:) while the one that is not working on has multiple drives and the drive I'm seeing the error on is a non-system drive (D:\ drive instead of C:\ drive). I can test the system drive on my mult-drive machine later today to see if that helps at all. |
It's a bug in Node.js which was fixed in nodejs/node#41221 and shipped in Node.js v14.19.2, v16.14, and v17.4. |
Ah, thanks @merceyz! |
Upgrading to node v16.19.0 fixed it for me, thanks @merceyz! |
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. |
Version
29.3.1
Steps to reproduce
Expected behavior
Yarn runs tests
Actual behavior
Yarn does not start, terminal hangs
Additional context
See repo https://github.com/aboe026/jest-npm-typescript-test for similar jest setup but with npm instead of yarn, notice jest runs as it should.
Environment
The text was updated successfully, but these errors were encountered: