How to Fix pnpm Command Not Found on macOS Without Reinstalling Node Three Times and Still Missing Corepack

Why this happens so often: modern Node tooling gives you several ways to get pnpm, and mixing them badly is how you end up with Node working, npm working, and pnpm somehow still missing.

Typical symptom:

pnpm: command not found

Step 1: verify Node itself first

node -v
npm -v
which node
which npm

If Node is missing or points somewhere unexpected, fix that before chasing pnpm specifically.

Step 2: prefer Corepack on modern Node

On newer Node versions, the cleanest path is usually:

corepack enable
corepack prepare pnpm@latest --activate
pnpm -v

If corepack itself is missing, your Node install may be older or incomplete.

Step 3: if you used npm global install, inspect PATH

npm config get prefix
echo $PATH

If the npm global bin directory is not on your PATH, the package may be installed but not executable from your shell.

Step 4: reload the shell after changes

source ~/.zshrc
hash -r

Without that, the shell may keep remembering the old command state.

What not to mix casually

Be careful with:

1. Homebrew Node
2. nvm Node
3. npm global binaries
4. old shell PATH hacks

One machine can accumulate all four and make basic tooling look haunted.

Bottom line

If pnpm is missing on macOS, first verify Node, then use Corepack, then fix PATH only if you truly need a global binary directory. Most broken setups are path confusion, not pnpm itself.

Sources

• pnpm installation docs
• Corepack docs