[Bug?]: Timeouts when using PnP with ESM on Node <=16.14

[franciscofabian]

Self-service

• I'd be willing to implement a fix

Describe the bug

Running jest tests in CI always timeout (10 minutes) with yarn 3.2.0, running with 3.1.1 and earlier versions it finishes in less than 10 seconds.

To reproduce

yarn jest

Environment

CircleCI 2.1

Additional context

No response

[RDIL]

Can you please provide a repository which exhibits the behavior?

[franciscofabian]

I have fixed the issue adding the option --maxWorkers=1 in jest. I tried to set up a new repository to reproduce the behavior but with the same code an setup and couldn't reproduce, I'm not sure why yet. Is there any change in yarn 3.2.0 that could had caused the process not to exit when running in multiple workers?

[psychobolt]

I think I am also seeing the same issue on the rollup-terser-plugin, which utilizes jest workers as well... hmm

[arcanis]

Does it work if you either disable esm support in your yarnrc, or upgrade to the very latest Node 16.x release?

[franciscofabian]

Yes! It works for me either disabling esm support in my yarmrc or upgrading to the latest Node (v16.14.0 from v16.2.0)

[arcanis]

Then it's caused by nodejs/node#41134

More details in this other thread: vercel/next.js#34688 (comment) (not related to Next.js, just discussion occurred there).

[merceyz]

To have it written in this issue as well:
This issue was fixed in nodejs/node#41221 which has shipped in Node.js v14.19.2, v16.14, and v17.4.

[sublimator]

This issue was fixed in nodejs/node#41221

Will this be fixed in 14 LTS ?

[merceyz]

I don't know, this is the wrong place to ask.

[sublimator]

Fair enough, thanks