Vovy finds why your Mac cannot see a tool, usually a missing PATH line in ~/.zshrc or ~/.zprofile, fixes it, and explains what PATH is.
Terminal keeps saying command not found for npm, what's wrong
How it works
- Find out if the tool exists: Vovy searches the usual install folders like /opt/homebrew/bin and ~/.nvm to see whether the tool is missing or just hidden.
- Read your PATH: PATH is the list of folders your shell searches for commands. Vovy prints it and highlights which folder is missing.
- Fix your shell profile: Vovy adds the right line to ~/.zprofile or ~/.zshrc, such as the brew shellenv or nvm lines, and removes duplicates left by old installers.
- Install it if truly missing: If the tool is not on your Mac at all, Vovy installs it with the right method, like Homebrew for git or nvm for npm.
- Test in a fresh window: Vovy opens a new Terminal window and runs the command again, then shows a before-and-after card of your PATH.
What you provide
- The command that failed
- The full error message
What you get
- The command working in every new window
- A clean ~/.zshrc or ~/.zprofile
- PATH explained in plain English
- Duplicate installs flagged
FAQ
It worked yesterday, why not today?
Usually a new Terminal window is not loading the line that an installer added only to your old session, or a macOS update reset something.
What is the difference between .zshrc and .zprofile?
.zprofile runs once when you log in to a shell, .zshrc runs for every interactive window. Homebrew uses .zprofile, nvm uses .zshrc.
Could editing these files break Terminal?
A typo can cause errors, which is why Vovy backs up the file first and tests in a fresh window.
Related tasks
All tasks