npm ERR! code EBUSY

npm cannot access a file because it is being used.

Frequently documented in developer and vendor support forums.

• Editor has file open
• Antivirus scanning
• Another npm process

1. Close all editors
2. Stop other npm processes
3. Restart computer if needed

Last reviewed: March 2026 How we review solutions

EBUSY stands for "Error BUSY" and comes from the operating system when npm attempts to modify a file or directory that another process currently has locked. This is a file system-level error, not an npm-specific one—npm simply surfaces what the OS reports. On Windows, this error is significantly more common than on macOS or Linux because Windows enforces mandatory file locking: if any process has a file open for reading or writing, no other process can delete or rename that file. The most common culprit is another npm process running simultaneously—if you open two terminal windows and run npm install in both, the second process will fail with EBUSY when it tries to modify node_modules files that the first process has locked. IDE file watchers (VS Code, WebStorm) are the second most frequent cause: these tools keep handles open to files inside node_modules for indexing and IntelliSense, preventing npm from replacing or deleting those files during installation. Antivirus software on Windows is another major source—real-time scanning locks each file briefly as npm writes it, and if npm tries to rename or delete the file during that scan window, the OS returns EBUSY.

1. Close all other terminal windows that might be running npm commands
2. Close your IDE or disable its node_modules file watching temporarily
3. Check for antivirus real-time scanning and exclude the project directory
4. On Windows, use Task Manager to check for node.exe processes and end stale ones
5. Wait 10-30 seconds and retry — the lock may be transient

Docker volume mount on Windows

When using Docker with Windows volumes mounted to Linux containers, file locking behaves unpredictably. npm install inside the container may fail with EBUSY on mounted volumes. Use named Docker volumes instead of bind mounts for node_modules, or run npm install inside the container with node_modules excluded from the mount.

Git hooks running npm scripts

If a pre-commit or post-merge Git hook runs npm install while you are already running npm commands, both processes compete for the same files. Disable hooks temporarily with git commit --no-verify or serialize the operations.

OneDrive or Dropbox syncing node_modules

Cloud sync tools like OneDrive and Dropbox lock files during upload. If your project is inside a synced folder, npm cannot modify files that are being uploaded. Move projects outside synced folders or exclude node_modules from syncing.

How do I find what locks files?

Use lsof on Mac/Linux or Process Explorer on Windows.

Can I force npm?

Better to find and close the locking process.

Why does EBUSY happen more on Windows than macOS or Linux?

Windows uses mandatory file locking—any process reading a file prevents other processes from deleting or renaming it. macOS and Linux use advisory locking, which allows processes to modify files even if another process has them open.

Can I prevent EBUSY errors permanently?

Exclude your project directory from antivirus scanning, disable IDE file watching for node_modules, and avoid running multiple npm processes in the same project. These three steps eliminate the vast majority of EBUSY errors on Windows.

Is it safe to force-delete node_modules when EBUSY occurs?

Yes, deleting and recreating node_modules is always safe. If rmdir fails because of locks, try closing all terminals and IDEs first, or restart your machine to release all file handles. Then run npm install fresh.

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