[Error]: spawn EINVAL -4071

[DarekDan]

Describe the bug

While running tsp install right after tsp init (a new clean project) on Windows 11 (details below) with Node 20.12.2, I am getting the following error:

Error: spawn EINVAL
at ChildProcess.spawn (node:internal/child_process:421:11)
at spawn (node:child_process:761:9)
at installTypeSpecDependencies (file:///D:/Scratch/TypeSpec/node_modules/@typespec/compiler/dist/src/core/install.js:4:19)
at file:///D:/Scratch/TypeSpec/node_modules/@typespec/compiler/dist/src/core/cli/cli.js:157:95
at Object.handler (file:///D:/Scratch/TypeSpec/node_modules/@typespec/compiler/dist/src/core/cli/utils.js:16:16)
at file:///D:/Scratch/TypeSpec/node_modules/yargs/build/lib/command.js:206:54
at maybeAsyncResult (file:///D:/Scratch/TypeSpec/node_modules/yargs/build/lib/utils/maybe-async-result.js:9:15)
at CommandInstance.handleValidationAndGetResult (file:///D:/Scratch/TypeSpec/node_modules/yargs/build/lib/command.js:205:25)
at CommandInstance.applyMiddlewareAndGetResult (file:///D:/Scratch/TypeSpec/node_modules/yargs/build/lib/command.js:245:20)
at CommandInstance.runCommand (file:///D:/Scratch/TypeSpec/node_modules/yargs/build/lib/command.js:128:20) {
errno: -4071,
code: 'EINVAL',
syscall: 'spawn'
}

It seems similar to an error mentioned here: https://blogs.namitoyokota.com/error-spawn-einval

Could you please look into it and see if it will require similar resolution?

Edition Windows 11 Pro
Version 23H2
Installed on ‎6/‎30/‎2023
OS build 22631.3527
Experience Windows Feature Experience Pack 1000.22700.1003.0

Reproduction

1. Create new directory
2. Execute tsp init with defaults (see Getting Started)
3. Execute tsp install

Checklist

• Follow our Code of Conduct
• Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion.
• The provided reproduction is a minimal reproducible example of the bug.

[DarekDan]

I have confirmed that manually adding shell: true resolved the problem. Will be submitting PR shortly.

[DarekDan]

No need for action. Issue related to #3243