"No such file or directory" error while using npm

Question

I installed node and npm using the instructions provided here

I was able to use node successfully. However, as I attempt to install the "Formidable" node module, I get the following error:

$npm install formidable
bash: /usr/local/bin/npm: /usr/local/bin/node: bad interpreter: No such file or directory

When I do a which npm I get the following output:

$which npm
/usr/local/bin/npm

I have no clue on what is wrong with npm here - any idea on how I can fix this?

Welcome to Ask Ubuntu! I see you've installed Node in `/usr/local/bin/`. [The packages](https://launchpad.net/~chris-lea/+archive/node.js/+packages?field.name_filter=&field.status_filter=published&field.series_filter=quantal) as you used in the instructions you linked to don't do this. I think you've installed another Node from source as well. Please tell the whole story. — gertvdijk, Feb 03 '13 at 21:54
@gertvdijk Well, there was node 0.8.14 installed initially. I wanted to upgrade this to 0.8.18. I then ran `$sudo apt-get remove --purge nodejs npm` but this did not work. `node --version` after installing 0.8.18 still showed 0.8.14. So, what I did was follow a post which I can't find now - it basically instructed to do `which node` followed by `rm -r /usr/local/bin/...` - basically some node related files under that directory. Now, after this, i re-installed node and it was the updated version. Its working fine, but npm isn't. — user109187, Feb 04 '13 at 15:06
Yeah this is what happens when you install from source. It will confuse your package management and you as a user. Please only install software as packages unless you know what you're doing. Use the uninstall instructions with the scripts you used to install this earlier version to properly uninstall it. And please **edit** your question to provide further information. This is a Q&A site, not a discussion forum, you see? :) — gertvdijk, Feb 04 '13 at 15:07
@gertvdijk I found the post which instructed to manually remove the files - http://stackoverflow.com/a/5917184/1907800. The path here is /usr/bin/node — user109187, Feb 04 '13 at 15:08
Note to myself for when I come back here in a week. Close the terminal and reopen it — Tofandel, Aug 11 '21 at 10:23

score 93 · Accepted Answer · edited May 23 '17 at 12:39

93

Taking @gertvdijk hint, I uninstalled NPM using the script:

rm -rf /usr/local/{lib/node{,/.npm,_modules},bin,share/man}/npm*

(which can be found here)

Even after performing the above, I got another error:

$ npm install formidable  
bash: /usr/local/bin/npm: No such file or directory

So, I ran hash -r in the terminal (as per the instructions found under NPM Won't Run After Upgrade) and voila - it worked. NPM now works!

edited May 23 '17 at 12:39

Community

1

answered Feb 04 '13 at 15:28

user109187

1,621
1
11
8

1

the only useful thing here was discovering `hash`, which can be simply used to point to another node/npm (what if I wish to work with more than one version of node?) – user309383 May 25 '16 at 20:55
Beautiful guest user. – LM_Fielding Jun 18 '17 at 18:17
11

hash -r saved me – diogo.abdalla Jul 19 '18 at 17:42
what does `hash` does!? – Chanjung Kim Mar 29 '19 at 06:41
2

What is hash? It worked like magic, but I don't know how it works – Precious Tom Apr 17 '20 at 16:04
HASH! Perfecto. – Allen Gingrich Feb 04 '21 at 00:19
god bless hash -r – TurtleLoop Jan 01 '22 at 10:42

score 11 · Answer 2 · edited May 11 '14 at 16:13

11

Ubuntu and some Linux distributions install node's interpreter as /usr/bin/nodejs, and not /usr/local/bin/node.

You can solve this issue installing the nodejs-legacy package which creates a symlink from /usr/bin/nodejs to /usr/bin/node.

Solution:

sudo apt-get install nodejs-legacy

References: nodejs-legacy package

edited May 11 '14 at 16:13

jkt123

3,460
22
24

answered May 11 '14 at 15:49

Pac

111
1
2

4

It seems `nodejs-legacy` no longer exists. – Martín De la Fuente Mar 28 '19 at 23:15

score 10 · Answer 3 · answered Dec 09 '20 at 12:47

10

step 1: run npm -v o/p : Error: bash: /usr/local/bin/npm: No such file or directory

step 2: run which npm o/p: /usr/bin/npm

step 3: run hash -r then run npm -v o/p : 3.5.2

answered Dec 09 '20 at 12:47

Anmol Mourya

211
2
5

Thank you very much! – AlexKh Aug 14 '21 at 12:32
what is the use of hash -r? – Amitkumar solanki Jan 08 '22 at 06:09

score 2 · Answer 4 · answered Feb 04 '13 at 15:12

It appears that you've installed another Node version from source some time earlier. This is indicated by the /usr/local/bin path where it appears to be installed now.

Uninstall the one you installed from source. See the instructions that got with the source on how to do so. There's no single way on how to uninstall software scripts installed which don't work with your system's package management.
Install the packages with are listed in the instructions you linked to in your question.
Verify that which npm now lists /usr/bin as installation path.

In general you should never have to install packages from source. And if you do, please be aware of the consequences as you're overriding the package management here an it will get confused by it.

"No such file or directory" error while using npm

4 Answers4