error hub
Recurring ENOENT errors
A graph-derived KFA hub for recurring ENOENT evidence across distinct public record types.
Common Problems
- Missing executable is reported on the ChildProcess error event
When child_process.spawn receives a command that cannot be resolved, the call can return a ChildProcess before the failure is delivered. Attach an error listener immediately and handle error code ENOENT; do not rely only on synchronous exceptions or the close event.
- How should ENOENT distinguish a missing executable from a missing working directory?
## Question How should ENOENT distinguish a missing executable from a missing working directory? ## Why this matters Recurring public developer task for HTTP and integration errors. ## Environment / product HTTP and integration errors ## What needs to be determined Current researched guidance, applicability, limitation
- MCP TypeScript client custom env removes PATH and causes spawn npx ENOENT
## Problem - MCP TypeScript client custom env removes PATH and causes spawn npx ENOENT ## Observed symptom - The stdio connection works without env overrides and fails with spawn npx ENOENT when a custom env is supplied. - Observed in 1 reviewed public artifact; this is not a claim that only that many reports exist. ##
- spawn npx ENOENT in a desktop MCP client while the terminal works
## Problem - spawn npx ENOENT in a desktop MCP client while the terminal works ## Observed symptom - A desktop editor/client reports spawn npx ENOENT, but npx resolves in an interactive terminal. - Observed in 3 reviewed public artifacts; this is not a claim that only that many reports exist. ## Exact error or signatur
- Claude Desktop cannot resolve npx installed through a shell version manager
## Problem - Claude Desktop cannot resolve npx installed through a shell version manager ## Observed symptom - npx works in fish/zsh, but Claude Desktop reports spawn npx ENOENT for npm MCP servers. - Observed in 2 reviewed public artifacts; this is not a claim that only that many reports exist. ## Exact error or signa
- VS Code remote MCP host cannot find npx that exists on the local machine
## Problem - VS Code remote MCP host cannot find npx that exists on the local machine ## Observed symptom - An MCP server starts or resolves locally, but the Remote/WSL/Dev Container/SSH extension host reports ENOENT or launches in the wrong place. - Observed in 3 reviewed public artifacts; this is not a claim that onl
- Bare npx command fails to launch MCP servers on Windows
## Problem - Bare npx command fails to launch MCP servers on Windows ## Observed symptom - A Windows MCP host reports spawn npx ENOENT or EINVAL while a shell or explicit Node executable can start the server. - Observed in 4 reviewed public artifacts; this is not a claim that only that many reports exist. ## Exact erro
Solutions with evidence
- Researched guidance: How should ENOENT distinguish a missing executable from a missing working directory?
## Summary Node.js child_process documents the same ENOENT for a missing command and a nonexistent cwd; the error text may name the command even when cwd is the cause. Distinguish them with a bounded, post-failure inspection of the exact cwd and executable resolution, while treating the result as diagnostic rather than