Error troubleshooting npm install

—

## 🔴 Key Errors Identified:

### 1. **EBUSY / EPERM: Resource busy or operation not permitted**

[Error: EBUSY: resource busy or locked, rmdir 'D:mybell-mobility-upgrade-hardware...']
[Error: EPERM: operation not permitted, rmdir 'D:mybell-mobility-upgrade-hardware...']

These errors happen when:
– A file or folder is **locked** (often by antivirus or a background process like VSCode or your terminal).
– You **don’t have permission** (even if you're in Admin mode).

—

### 2. **npm ERR! code E403: Forbidden access to npm registry**

npm ERR! code E403
npm ERR! 403 Forbidden: GET https://registry.npmjs.org/term-size/-/term-size-2.1.2.tgz

This is a **network access error** — usually caused by:
– A **firewall** or **Zscaler**/proxy blocking npm registry.
– You're on a **corporate network** with restricted access.

—

## ✅ Recommended Fixes

### 🔁 Step-by-step Solution:

—

### ✅ A. Fix `EBUSY` / `EPERM` (File Locked/Permission Denied)

1. **Close all running apps** that might lock the files:
– VS Code
– File Explorer (close any folder opened to `D:mybell…`)
– Git clients or terminals

2. **Reboot your PC**, then immediately open **Command Prompt as Administrator** and run:

npm cache clean --force

3. **Manually delete the `node_modules` and `package-lock.json`:**

rd /s /q node_modules
   del package-lock.json

Or delete them from Windows File Explorer manually.

—

### ✅ B. Fix `E403` npm registry access

You’re behind a proxy or firewall (e.g., **Zscaler**, corporate VPN).

1. Set your registry explicitly:

npm config set registry https://registry.npmjs.org/

2. If you use a proxy (check with IT or network admin), configure npm to use it:

npm config set proxy http://your.proxy:port
   npm config set https-proxy http://your.proxy:port

3. If you're using **Zscaler**, try disabling it temporarily (if allowed), or switch to a **mobile hotspot** to bypass network blocks and run the command again.

4. Try using a mirror:

npm install --registry=https://registry.npmmirror.com

—

## ✅ Final Retry

After all fixes:

npm install
npm linklocal --force

—

## ✅ Bonus: Use PowerShell Admin for fewer permission issues

Instead of Command Prompt, try:

1. Open **Windows PowerShell as Administrator**.
2. Navigate to your folder.
3. Run the same `npm` commands.

—

Let me know if you're on a **corporate VPN** or using **Zscaler** — I’ll tailor a workaround accordingly.