How to fix npm ERR! ENOENT: no such file or directory in npm

npmBEGINNERLOWUpdated Dec 6, 2025· 117 views

The ENOENT cache error occurs when npm's cache directory is missing or inaccessible. Clearing and rebuilding the cache usually resolves this issue.

Quick fix

Fixes npm ERR! ENOENT: no such file or directory

npm config get cache

# Check if directory exists
ls -la $(npm config get cache)

Verify cache location
Clean the cache
Reset cache location
Fix permissions

npm — error

$npm config get cache
# Check if directory exists
ls -la $(npm config get cache)
npm ERR! ENOENT: no such file or directory

What this error means

npm maintains a cache of downloaded packages to speed up future installations. When the cache directory or specific cached files are missing or corrupted, npm may fail with ENOENT errors during cache operations. This can happen after system cleanups, disk errors, or when cache paths are misconfigured.

Typical symptoms

npm install fails with cache ENOENT
Cache operations fail
npm cache verify shows errors
Error points to .npm cache path
Problem after disk cleanup
Multiple users sharing cache

Common causes

Cache directory deleted
Cache path misconfigured
Disk errors corrupted cache
Insufficient permissions
Shared cache between users
Docker volume issues
Symlink target missing

How to fix "npm ERR! ENOENT: no such file or directory"

1Verify cache location

Check cache configuration:

bash

npm config get cache

# Check if directory exists
ls -la $(npm config get cache)

2Clean the cache

Clear and rebuild:

bash

npm cache clean --force

# Verify cache
npm cache verify

3Reset cache location

Set to default or new location:

bash

# Reset to default
npm config delete cache

# Or set new location
npm config set cache /path/to/new/cache

4Fix permissions

Ensure proper access:

bash

# Check permissions
ls -la ~/.npm

# Fix if needed
sudo chown -R $(whoami) ~/.npm
chmod -R u+rwX ~/.npm

5Recreate cache directory

Manually create if missing:

bash

mkdir -p ~/.npm/_cacache
mkdir -p ~/.npm/_logs

6For Docker/CI environments

Ensure cache persistence:

yaml

# Docker volume
volumes:
  - npm-cache:/root/.npm

# GitHub Actions
- uses: actions/cache@v3
  with:
    path: ~/.npm
    key: npm-cache-\${{ hashFiles('**/package-lock.json') }}

Advanced notes

npm's cache is content-addressable, making it safe to delete entirely. The cache grows unbounded - periodic npm cache clean may be needed. In CI, cache warming speeds up builds but stale caches can cause issues. Multi-user systems should have separate caches or use npm's --cache flag per-user. Docker builds benefit from caching the npm cache directory.

Frequently asked questions

What does "npm ERR! ENOENT: no such file or directory" mean?: npm maintains a cache of downloaded packages to speed up future installations. When the cache directory or specific cached files are missing or corrupted, npm may fail with ENOENT errors during cache operations. This can happen after system cleanups, disk errors, or when cache paths are misconfigured.
How do I fix "npm ERR! ENOENT: no such file or directory"?: The ENOENT cache error occurs when npm's cache directory is missing or inaccessible. Clearing and rebuilding the cache usually resolves this issue.
What causes "npm ERR! ENOENT: no such file or directory"?: Cache directory deleted Cache path misconfigured Disk errors corrupted cache
Is the "npm ERR! ENOENT: no such file or directory" error serious?: It is a low-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading