How to fix npm ERR! code EBUSY npm ERR! EBUSY: resource busy or locked in npm

The simplest solution is to close all open terminals, command prompts, and IDEs accessing your project.

Visual Studio Code:
Click the trash bin icon in the terminal tab to properly close it (clicking the X may keep it running in the background).

All terminals:
Close PowerShell, Command Prompt, Git Bash, and any other terminal windows.

Then try your npm command again:

npm install

Delete the node_modules directory and package-lock.json, then clear the npm cache:

# Windows PowerShell
Remove-Item -Recurse -Force node_modules
Remove-Item package-lock.json
npm cache clean --force

# Windows Command Prompt
rmdir /s node_modules
del package-lock.json
npm cache clean --force

After clearing everything, reinstall:

npm install

Antivirus software like Windows Defender, AVG, Bullguard, or HP Wolf Security can lock files during scanning.

Windows Defender:
1. Open Windows Security (search in Start menu)
2. Click "Virus & threat protection"
3. Under "Virus & threat protection settings," click "Manage settings"
4. Toggle off "Real-time protection"
5. Run your npm command
6. Toggle real-time protection back on when done

If disabling antivirus fixes the issue, add your project folder to the antivirus exclusion/whitelist.

Cloud storage services like Dropbox, OneDrive, and Google Drive hold locks on files while syncing:

Pause synchronization:
- Dropbox: Click the icon in system tray → Pause syncing
- OneDrive: Click the icon in system tray → More → Pause syncing
- Google Drive: Stop Google Drive temporarily

Then try npm install:

npm install

Better solution: Move your project outside synced folders (e.g., to C:\Users\YourName\Projects instead of C:\Users\YourName\Dropbox\Projects).

Some background processes lock files in node_modules. Check Task Manager:

1. Press Ctrl+Shift+Esc to open Task Manager
2. Look for these common lock-holders:
- Java(TM) Platform SE Binary
- Electron processes
- Python processes
- Previous npm or node processes
3. Select each and click "End Task"

Or use PowerShell as Administrator:

# End all Node processes
Stop-Process -Name "node" -Force

# End all npm processes
Stop-Process -Name "npm" -Force

If all else fails, run your terminal with elevated privileges and restart your system:

Run PowerShell as Administrator:
1. Press Windows key, search for "PowerShell"
2. Right-click the result and select "Run as administrator"
3. Navigate to your project directory:

cd "C:\Users\YourName\path\to\project"
npm install

Restart your computer:
This clears all file locks held by processes:

Restart-Computer

After restarting, open a fresh terminal and try npm install again.