The invalid cwd path is not reported correctly.

[JacksonTian]

Version

v18.19.0

Platform

Darwin local.local 23.1.0 Darwin Kernel Version 23.1.0: Mon Oct 9 21:27:24 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T6000 arm64

Subsystem

child_process

What steps will reproduce the bug?

const { spawn } = require('child_process');

spawn('echo hello', {
    cwd: '/invalid_path'
});

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

No response

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

Report the cwd path is invalid.

What do you see instead?

$ node test.js 
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: spawn echo hello ENOENT
    at ChildProcess._handle.onexit (node:internal/child_process:284:19)
    at onErrorNT (node:internal/child_process:477:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Emitted 'error' event on ChildProcess instance at:
    at ChildProcess._handle.onexit (node:internal/child_process:290:12)
    at onErrorNT (node:internal/child_process:477:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'spawn echo hello',
  path: 'echo hello',
  spawnargs: []
}

Node.js v18.19.0

The error message make me confuse.

Additional information

No response

[richardlau]

Duplicate of #45279 and may be unfixable, see #45279 (comment).

[pluris]

IMO, how about adding the typed cwd to the error message?
cwd: '/invalid_path'