Node 21.7.3 breaks spawnSync with error EINVAL

[arthurfiorette]

Version

21.7.3

Platform

Microsoft Windows NT 10.0.22631.0 x64

Subsystem

No response

What steps will reproduce the bug?

Hello! This is my first nodejs issue so I'm not sure what can be useful to reproduce this bug. However, I happened in a public repo with Ci running on both node 20 and node 21.

Run using node 21.7.2:

Node version log: https://github.com/kitajs/kitajs/actions/runs/8628576466/job/23650948977#step:4:13
Test passed: https://github.com/kitajs/kitajs/actions/runs/8628576466/job/23650948977#step:8:144

Run using node 21.7.3:

Node version log: https://github.com/kitajs/kitajs/actions/runs/8628576466/job/23711050372#step:4:13
Test failed: https://github.com/kitajs/kitajs/actions/runs/8628576466/job/23711050372#step:8:19

---

I could try to setup a minimal reproducible example, is there a template somewhere I could follow?

How often does it reproduce? Is there a required condition?

Never with 21.7.2 and always with 21.7.3

What is the expected behavior? Why is that the expected behavior?

No response

What do you see instead?

error: Error: spawnSync D:\a\kitajs\kitajs\packages\cli\bin\dev.cmd EINVAL
at Object.spawnSync (node:internal/child_process:1124:20)
at spawnSync (node:child_process:876:24)
at TestContext. (D:\a\kitajs\kitajs\packages\cli\test\build\index.test.ts:9:24)
at Test.runInAsyncScope (node:async_hooks:206:9)
at Test.run (node:internal/test_runner/test:639:25)
at Test.start (node:internal/test_runner/test:550:17)
at startSubtest (node:internal/test_runner/harness:218:17) {
errno: -4071,
code: 'EINVAL',
syscall: 'spawnSync D:\\a\\kitajs\\kitajs\\packages\\cli\\bin\\dev.cmd',
path: 'D:\\a\\kitajs\\kitajs\\packages\\cli\\bin\\dev.cmd',
spawnargs: [ 'build' ]

Additional information

The file being spawned:

https://github.com/kitajs/kitajs/blob/6a23155b8f220793b03738b09e3d3b0b11724b07/packages/cli/bin/dev.cmd

[arthurfiorette]

Oops... Seems that this issue is already reported: #52470 and node-red/node-red#4652

[benjamingr]

Correct