ENOSPC npm Origin: Build & delivery Last updated 12 Oct 2026

Error: ENOSPC: System limit for number of file watchers reached

Linux ran out of inotify watches — dev servers watching large projects hit the limit.

Exact message you may see System limit for number of file watchers reachedENOSPC: System limit
Seen on: npm

Meaning

Not disk space: it’s fs.inotify.max_user_watches (often 8192). Webpack/Vite/Jest watching node_modules exhausts it.

Common causes

  • Low inotify limit
  • Watching node_modules or large folders
  • Many projects/IDEs watching at once

⚡ Quick fix

  1. Raise the limit: fs.inotify.max_user_watches=524288
  2. Exclude node_modules from watchers

Detailed fix by platform

Linux

  1. echo fs.inotify.max_user_watches=524288 | sudo tee /etc/sysctl.d/99-inotify.conf && sudo sysctl --system

How to diagnose

  1. Limit — cat /proc/sys/fs/inotify/max_user_watches
  2. Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Build & delivery. Errors that are often confused with or caused by this one (click to open):

cb() never called — npm ERR! cb() never called! (npm)cb() never calledCorepack keyid — Error: Cannot find matching keyid (Corepack signature verification) (npm)Corepack keyidE401 — npm ERR! code E401 — Unable to authenticate, need: Basic realm / Incorrect or missing password (npm)E401E402 — npm ERR! code E402 — 402 Payment Required - PUT https://registry.npmjs.org/@scope%2fpkg - You must sign up for private packages (npm)E402E403 — npm ERR! code E403 — 403 Forbidden - PUT https://registry.npmjs.org/x - You do not have permission to publish (npm)E403E404 — npm ERR! code E404 — 404 Not Found: package@version is not in this registry (npm)E404ENOSPC — no space left on device (Docker / Linux) (Docker)ENOSPCENOSPC

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.