Summary

When the current working directory is deleted or unmounted while a Node.js process is running, process.cwd() throws:

Error: ENOENT: no such file or directory, uv_cwd
    at process.wrappedCwd [as cwd] (node:internal/bootstrap/switches/does_own_process_state:142:28)

The error references uv_cwd (a libuv internal) but never mentions process.cwd() or explains that the directory was deleted. This is confusing to debug, especially when triggered deep in dependency code.

Changes

lib/internal/bootstrap/switches/does_own_process_state.js

Wraps the rawMethods.cwd() call in wrappedCwd() to catch ENOENT and throw a descriptive error:

• Sets message to: "The current working directory does not exist. It may have been deleted or unmounted. Change to an existing directory and try again."
• Sets syscall to process.cwd instead of uv_cwd
• Preserves err.code (ENOENT) so existing programmatic checks still work
• Re-throws non-ENOENT errors unchanged

Before:

Error: ENOENT: no such file or directory, uv_cwd

After:

Error: The current working directory does not exist. It may have been deleted or unmounted. Change to an existing directory and try again.

test/parallel/test-process-cwd-enoent.js (new)

Regression test that:

1. Creates a temp directory
2. Spawns a child process that chdirs into it, deletes it, and calls process.cwd()
3. Asserts the error has code: 'ENOENT', syscall: 'process.cwd', and a message mentioning "current working directory"
4. Skipped on Windows (Windows does not allow deleting cwd of a running process)

Fixes: #57045

Made with Cursor