npm ERR! code ENOENT

npm tried to access a file or directory that does not exist on your system.

Frequently documented in developer and vendor support forums.

• Missing package.json file
• Corrupted node_modules folder
• Wrong working directory

1. Ensure you are in the correct project directory
2. Run npm init if package.json is missing
3. Delete node_modules and reinstall

Last reviewed: March 2026 How we review solutions

ENOENT stands for "Error NO ENTry" and originates from the POSIX operating system standard. When npm reports this code, it means the tool tried to open a file or directory that does not exist on disk. The most common scenario is running npm install or npm start in a directory that has no package.json file—npm needs this manifest to know what to install or which script to run. Corrupted or partially deleted node_modules directories trigger ENOENT as well: npm expects certain files inside the dependency tree, and if a previous install was interrupted or a manual deletion removed some but not all files, the remaining references point to gaps. Symbolic links that target deleted folders are another frequent source, particularly on Windows where junction points can become stale after moving projects between drives. Git operations that remove tracked files without updating the working tree can leave npm pointing at paths that existed in a previous commit but no longer exist locally. The fix almost always involves verifying your working directory, ensuring package.json exists, and clearing stale state with a clean reinstall.

1. Run pwd (or cd on Windows) to confirm you are in the project root
2. Verify package.json exists in the current directory with ls package.json
3. Check the full error output for the exact missing file path
4. Delete node_modules and package-lock.json, then run npm install fresh
5. If using workspaces, ensure you are in the correct workspace directory

Monorepo with hoisted dependencies

In a monorepo using npm workspaces, running npm install from a nested package directory instead of the root can produce ENOENT because hoisted dependencies live in the root node_modules. Always install from the workspace root.

Case-sensitive file system mismatch

macOS defaults to case-insensitive file systems, but Linux is case-sensitive. A package.json referencing "./Utils/helper" will work on macOS but fail with ENOENT on Linux CI if the actual directory is "./utils/helper".

Git sparse checkout or shallow clone

If your CI uses git clone --depth 1 or sparse checkout, files referenced by npm scripts or postinstall hooks may not be present in the checkout, causing ENOENT during the build step.

What causes ENOENT?

ENOENT means "Error NO ENTry" - the requested file or directory was not found.

How do I fix missing package.json?

Run npm init -y to create a new package.json with default values.

What does "syscall open" mean in the ENOENT error?

It tells you which system call failed. "open" means npm tried to open a file for reading. Other syscalls like "lstat" or "rename" indicate directory listing or file move operations that failed because the target does not exist.

Why does ENOENT happen after switching Git branches?

Different branches may have different dependencies in package.json. After switching branches, the existing node_modules may reference packages that are no longer listed. Run npm install after every branch switch to sync dependencies.

Can ENOENT be caused by antivirus software?

Yes, on Windows, antivirus tools can quarantine or delete files inside node_modules during installation. If you see intermittent ENOENT errors, try adding your project directory to your antivirus exclusion list.

• npm install – Official npm Docs
• package.json Reference – npm Docs