Home/ Questions/Q 7078217
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T06:31:10+00:00

I’ve been using node .4x and npm, and decided to upgrade to .67. Oh

  • 0

I’ve been using node .4x and npm, and decided to upgrade to .67. Oh boy.

I’m on Mac OSX–new to it.

When I type npm I get

-bash: /usr/bin/npm: No such file or directory

echo $PATH shows a lot of stuff…some redundancies. 

/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin:/usr/local/git/bin:/Users/me/.rvm/bin:/usr/local/bin:/usr/local/:/usr/local/bin:/usr/local/bin/npm:/usr/local/bin/:/usr/local:/usr/local/bin:/usr/local/

I’ve tried a number of different installations, and likely should clean it up, which I don’t know how to do 🙂

Any insights?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If npm is no longer installed in /usr/bin/npm, then chances are good bash(1) has hashed the executable name. The hashing saves repeated searches of all directories in your PATH every time you execute common programs. Since programs almost never change directories, this is usually a great idea.

    To test, run hash -r. This will cause bash(1) to forget all its mappings. (This is harmless — it starts up with no mappings and grows them over time.) If I was right, your npm will execute the correct executable wherever it lives.

    • 0