Azure / Azure/azure-functions-core-tools
Node 20.11 error: spawn Unknown system error
- Dominant language
- C#
- Stars
- 1.5k
- Forks
- 498
- Avg merge
- 5d 4h
- Merged PRs (30d)
- 15
Description
C:\users\\>func init --worker-runtime node
node:internal/child_process:421
throw errnoException(err, 'spawn');
^
Error: spawn UNKNOWN
at ChildProcess.spawn (node:internal/child_process:421:11)
at spawn (node:child_process:761:9)
at main (C:\Users\user_name\AppData\Roaming\npm\node_modules\azure-functions-core-tools\lib\main.js:9:22)
at Object. (C:\Users\user_name\AppData\Roaming\npm\node_modules\azure-functions-core-tools\lib\main.js:18:1)
at Module._compile (node:internal/modules/cjs/loader:1376:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1435:10)
at Module.load (node:internal/modules/cjs/loader:1207:32)
at Module._load (node:internal/modules/cjs/loader:1023:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:135:12)
at node:internal/main/run_main_module:28:49 {
errno: -4094,
code: 'UNKNOWN',
syscall: 'spawn'
}
Node.js v20.11.1
OS: Windows 11
CPU: I7
Contributor guide
Research direction
Reproduce `func init --worker-runtime node` on Windows 11 with Node.js 20.11.1 and review the reported spawn stack trace, especially the installed azure-functions-core-tools `lib/main.js` entry point. Done means identifying the cause of `Error: spawn UNKNOWN` and confirming that the initialization command completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, node.js
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100