Vibe coding · Terminal basics · For beginners

zsh: command not found: npm on a Mac? Here’s the Real Fix

Your Mac isn’t broken. Your terminal just doesn’t know where npm lives.

Three quick checks, three fixes, and the two mistakes that make “I already fixed it” still fail — each one reproduced in a real test terminal.

You know the feeling. Your AI assistant hands you a neat little plan: “Open Terminal and run npm install.” You find Terminal, paste the line, press Enter — and get one cold sentence back: zsh: command not found: npm.

No explanation. No next step. And the AI that told you to run it often assumes npm is already there. This error is not about your code — your project hasn’t even started yet. It’s about your terminal not being able to find a program. Once you see it that way, the fix is usually one of three things.

What “zsh: command not found: npm” actually means

Two words in that sentence need translating. zsh is the program behind your Terminal window — the thing that reads what you type. Apple says zsh is the default shell for all newly created user accounts starting with macOS 10.15 (Apple Support), which is why your error starts with “zsh:” and not “bash:”.

PATH is a list of folders. When you type npm, zsh walks through those folders one by one, looking for a file called npm. If it reaches the end of the list empty-handed, you get the error. That’s all it is.

Here’s the part that surprised me most in testing. I put a working copy of npm in a folder that wasn’t on the list, and zsh still said it didn’t exist — even though ls showed the file sitting right there:

% npm -v
zsh: command not found: npm

% ls ~/tools/node/bin/npm
/Users/you/tools/node/bin/npm     <- the file is right there

“Not found” means “not in the folders I check,” not “not on your computer.” Keep that in mind and every fix below makes sense.

(If your error has more than one line, or mentions a file instead of a command, it’s a different problem — how to read error messages when you can’t code walks through those.)

The 30-second check: which problem do you have?

Paste these one at a time. They only read information; they don’t change anything on your Mac.

node -v
npm -v
echo $PATH
ls /opt/homebrew/bin/npm /usr/local/bin/npm ~/.nvm

The first two are the version checks npm’s own docs recommend (npm Docs). The last line peeks into the usual places npm ends up. Now match what you see:

Fix 1: npm isn’t installed — install Node.js

npm isn’t a separate app you download. It comes bundled with Node.js. So if node -v is also “not found,” you don’t have an npm problem — you have a “nothing installed yet” problem, and that’s the easiest one to fix.

You have two common routes. The official installer from nodejs.org is the click-through option. npm’s own docs, though, take a clear side: “We strongly recommend using a Node version manager like nvm,” and they warn that Node installers can cause permission errors when you install packages globally (npm Docs).

My recommendation for vibe coders: go with nvm, because the people who make npm say so — but know that it has two traps of its own, which is exactly what Fix 2 covers. If you’d rather avoid the terminal entirely for now, the installer works too; just remember you chose it if permission errors show up later.

Fix 2: “nvm: command not found” right after installing nvm

This is the trap most beginners hit, and it’s not your fault. The nvm installer tries to write two lines into a hidden settings file in your home folder. On a fresh Mac, that file often doesn’t exist. nvm’s README says it plainly: since macOS 10.15 the default shell is zsh, nvm looks for .zshrc to update, and “none is installed by default” (nvm README, Troubleshooting on macOS).

I ran the official installer in a test account with no settings files. It did download nvm — and then printed this, which is very easy to scroll past:

=> Profile not found. Tried ~/.bashrc, ~/.bash_profile,
   ~/.zprofile, ~/.zshrc, and ~/.profile.
=> Create one of them and run this script again

# then, in a brand-new terminal window:
% nvm --version
zsh: command not found: nvm

The fix is the one nvm’s README gives: create the file, then run the install command again.

touch ~/.zshrc
# now re-run the install line from nvm's README, then
# close Terminal and open a new window

On my second run the installer reported it was appending its lines to .zshrc, and a new window answered nvm --version with 0.41.0.

The second trap: nvm works, npm still doesn’t

This one caught me in the same test. With nvm finally working, I typed npm -v — and got zsh: command not found: npm again. nvm is only the installer. Installing nvm does not install Node. You still have to ask it to:

nvm install --lts
node -v
npm -v

--lts means the long-term-support version, the stable one. (My test machine was blocked from nodejs.org, so this download is the one step I couldn’t complete myself; the command is the documented one.)

Fix 3: Node is installed, but npm isn’t on your PATH

If the ls line from the 30-second check found npm somewhere, the program exists — your PATH just doesn’t list its folder. Which folder depends on how you installed it:

To add a folder yourself, append one line to .zshrc. Replace the folder with the one your ls found:

echo 'export PATH="/opt/homebrew/bin:$PATH"' >> ~/.zshrc

Two details matter. Use two arrows, >> — that adds a line at the end. A single > replaces the whole file, wiping anything nvm or Homebrew put there. And keep :$PATH at the end, or you’ll replace your folder list instead of adding to it.

One more thing I learned the hard way in testing: you can’t dodge PATH by typing npm’s full address. When I ran npm by its full path, it failed with /usr/bin/env: 'node': No such file or directory. npm needs to find node on your PATH too — so fix the PATH, don’t work around it.

“I actually added it to PATH and it still doesn’t work”

This is the most frustrating version, because you did the fix. In my tests, it came down to one of two things.

1. You’re still in the same terminal window

zsh reads .zshrc when a window opens — not while you’re using it. In my test, I added the PATH line and ran npm -v in the same window: still “command not found.” Then I ran source ~/.zshrc (which says “re-read the file now”) and the very next npm -v printed 10.9.9. A brand-new window worked straight away too.

% echo 'export PATH="$HOME/tools/node/bin:$PATH"' >> ~/.zshrc
% npm -v
zsh: command not found: npm      <- same window, old settings
% source ~/.zshrc
% npm -v
10.9.9

So: after any change to .zshrc, open a new Terminal window before you decide it didn’t work. No need to restart the Mac.

2. You put the line in a bash file

Lots of older tutorials (and some AI answers) say to edit ~/.bash_profile. That file belongs to bash, the shell Macs used before zsh. I put the exact same PATH line in .bash_profile: bash found npm, zsh still said “command not found.” zsh’s manual lists the files it reads — .zshenv, .zprofile, .zshrc, .zlogin — and bash’s files aren’t among them (zsh manual, Startup Files).

On Windows instead? “npm is not recognized”

Windows says the same thing in different words: 'npm' is not recognized as an internal or external command. The idea is identical — Windows has its own PATH list — but the fix lives in a settings screen, not a hidden file. Start with how environment variables work on Windows, and as on a Mac, close and reopen your terminal after changing anything. I didn’t test Windows for this post.

npm works now. What’s the next error you’ll probably see?

Honestly, most people’s very next stop is this one. Once npm was found, I ran npm install in an empty folder:

npm error code ENOENT
npm error enoent Could not read package.json: Error: ENOENT:
  no such file or directory, open '.../Desktop/empty/package.json'

That’s good news in disguise: npm is installed and running. It just means you’re standing in the wrong folder. Use cd to move into your project folder (the one with package.json in it) and try again. If something breaks after that, here’s how to undo it when AI broke your working code.

The honest limitations

I reproduced every error here in zsh, but on a Linux test account, not a physical Mac. The behavior of PATH and .zshrc is the same shell logic, yet Mac-only details — Apple’s default settings, Homebrew’s folder, where the nodejs.org installer puts files — come from documentation, not my own machine. I couldn’t download Node through nvm because my test environment blocked nodejs.org. And I didn’t test Windows, code editors’ built-in terminals, or Macs managed by a company IT team, which can have extra rules.

Who should actually care

FAQ

Do I need to restart my Mac after fixing PATH?

No. Close the Terminal window and open a new one, or run source ~/.zshrc. In my test, either one picked up the change immediately.

Is it safe to edit .zshrc?

Yes, if you add lines rather than replace the file. Use >>, never a single >. If something goes wrong, the file is plain text — you can open it with open -e ~/.zshrc and delete the last line you added.

Should I use sudo to fix npm?

Not for this error. sudo doesn’t help zsh find a program that isn’t on PATH, and npm’s docs point to a version manager like nvm as the way to avoid global permission errors.

What’s the difference between .zshrc and .zprofile?

Both are zsh settings files. According to zsh’s manual, .zprofile is read by login shells and .zshrc by interactive shells. For a beginner adding one PATH line, .zshrc is the usual place; Homebrew may ask for .zprofile — follow what its installer prints.

Related free AI guides

• How to read error messages when you can’t code
• App works locally but not after deploy? 5 causes and fixes
• How to build an app without coding using AI

Published Nov 13, 2026. Tested in zsh 5.9 with Node v22.23.4 and the nvm v0.41.0 installer.