Step-by-Step Guide: Upgrading Angular CLI and Projects Using NVM for Node Management

🧱 Consider your Initial Setup: What You Had

• Old Angular CLI v13

• Old Node.js

• Existing Angular 13 project

---

🚀 Step-by-Step Guide

1. Install NVM (Node Version Manager for Windows)

• Download: https://github.com/coreybutler/nvm-windows/releases

• Run nvm-setup.exe and complete installation.

✅ Verify NVM

nvm version

---

2. Install & Use Supported Node.js Version

Angular 17 supports Node.js v20.

nvm install 20
nvm use 20
node -v    # Should show v20.x.x
npm -v     # Should show v10.x.x or v9.x.x

---

3. Uninstall Old Angular CLI (If Installed)

npm uninstall -g @angular/cli

---

4. Install Angular CLI v17 Globally

npm install -g @angular/cli@17

📦 Clean NPM Cache (Optional)

npm cache clean --force

---

5. Upgrade Angular 13 Project to Angular 17

📁 Go to your project folder

cd path/to/your-angular-project

🔄 Update Angular core & CLI

ng update @angular/core@17 @angular/cli@17

📝 Note: You may see additional suggestions — follow them one by one (like updating Angular Material or other dependencies).

---

6. Verify Everything

ng version

✅ Expected Output:

Angular CLI: 17.x.x
Angular: 17.x.x
Node: 20.x.x

---

📌 Bonus Commands

🧹 Clean Project Before Build (Optional)

rm -rf node_modules package-lock.json
npm install

---

📁 Switching Node Versions Anytime

nvm use 20     # Use Node.js v20
nvm use 14     # Example: switch to Node.js v14 if needed

---

✅ You are now set up for future Angular projects and upgrades using NVM and CLI version management.