[Bug]: Not starting with Yarn

[aboe026]

Version

29.3.1

Steps to reproduce

1. Clone repo https://github.com/aboe026/jest-yarn-typescript-test
2. Follow README

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

System:
    OS: Windows 10 10.0.22621
    CPU: (24) x64 AMD Ryzen 9 3900X 12-Core Processor
  Binaries:
    Node: 16.13.2 - ~\AppData\Local\Temp\xfs-495dcc21\node.CMD
    Yarn: 3.3.1 - ~\AppData\Local\Temp\xfs-495dcc21\yarn.CMD
    npm: 8.15.1 - C:\Program Files\nodejs\npm.CMD

[aboe026]

I also see the behavior if I unplug jest from PnP with yarn unplug jest

[aboe026]

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.

[SimenB]

Works for me as well:

---

This sounds more like a Yarn bug than a Jest one.

[merceyz]

It's a bug in Node.js which was fixed in https://github.com/nodejs/node/pull/41221 and shipped in Node.js v14.19.2, v16.14, and v17.4.

[SimenB]

Ah, thanks @merceyz!

[aboe026]

Upgrading to node v16.19.0 fixed it for me, thanks @merceyz!

[github-actions[bot]]

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. Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.