run npm command gives error "/usr/bin/env: node: No such file or directory"

[nickgit]

This happens in version 0.6.x on ubuntu. Does not happen above 0.7.x

[bnoordhuis]

Not a node bug. The node binary is not on your $PATH.

[digitalmediums]

I've found this is often a misnaming error, if you install from a package manager you bin may be called nodejs so you just need to symlink it like so "ln -s /usr/bin/nodejs /usr/bin/node"

[mtrovo]

digitalmediums,
That was useful, thanks a lot!

[houmie]

After 3 hours of suffering, this is the solution. Thank you digitalmediums. Why is this now misnaming happening now out of the blue?

[othiym23]

@houmie (and everyone who comes across this bug in the future)

These explain why:

http://lists.debian.org/debian-devel-announce/2012/07/msg00002.html
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614907
http://debian.2.n7.nabble.com/Node-js-and-it-s-future-in-debian-td1042211.html (only read this last thread if you're a masochist)

As a Node developer, I would think hard before using Debian's packaged version of node, and would use Ubuntu with chrislea's PPA for Node or Debian stable with Node built from source in preference to the stock Debian nodejs package for the foreseeable future. The discussion on this bug makes clear that Debian has a very different idea of the role of Node in the wider world than most of the Node community.

[houmie]

@othiym23 Thank you for the explanation. :) I see there is a proper flame war around this. But its understandable when namespaces are broken. Hope they can resolve it at one stage.

[micfan]

@digitalmediums Thx

[Augustin82]

Thanks for the help.

[JohnArcher]

@digitalmediums Thanks!

[johnjbarton]

I installed via sudo make install.

npm still fails:

/work/qpp$ sudo npm install -g grunt-cli
/usr/bin/env: node: No such file or directory
/work/qpp$ node -v
v0.10.4
/work/qpp$ which node
/usr/local/bin/node

[bnoordhuis]

@johnjbarton Try sudo PATH="$PATH:/usr/local/bin" npm install -g grunt-cli

[johnjbarton]

Thanks. However in the meantime I uninstalled node, unintalled npm, then
installed node and installed npm. Then I was able to install grunt-cli.

On Fri, Apr 12, 2013 at 2:13 PM, Ben Noordhuis notifications@gh.neting.ccwrote:

@johnjbarton https://github.com/johnjbarton Try sudo
PATH="$PATH:/usr/local/bin" npm install -g grunt-cli

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/3911#issuecomment-16317844
.

[arky]

Just do

$ sudo apt-get install nodejs-legacy

https://github.com/volojs/volo#install

[gw0]

Yes, installing nodejs-legacy is the cleanest solution.

Imho trying to name a server with a generic word like node is pretty stupid and it is quite understandable that there is so much resistance in accepting such a name. Rename it back to something unique that is easy to google for and can not be mistaken for something else, like nodejs, and everyone will be happy.

[bnoordhuis]

For very restricted definitions of 'everyone'. You're only two or three years late - that ship has long sailed.

[ForbesLindesay]

That ship sailed a long time ago and those arguments only really apply to something that's not vastly popular. node.js is popular enough to claim the node name and expect other less popular programs not to conflict with it.

As for not being googlable: https://www.google.com/?q=node

[amitmnnit]

Thanks,

[jarl-dk]

@othiym23 : Thanks for the details on ubuntu/debian...

[ebuildy]

I had to append /usr/bin to PATH in my PHP code :

putenv('PATH=' . getenv('PATH') . ':/usr/local/bin:/usr/bin');

[kevbob1]

"update-alternatives --install /usr/bin/node node /usr/bin/nodejs 99"

this fixed it for me

[rlidwka]

or just apt-get install nodejs-legacy

[rafee]

rlidwka's solution is the one, I arrived. Except the fact, I didn't see it & gone through infinite suffering.

[rlidwka]

rlidwka's solution is the one, I arrived. Except the fact, I didn't see it & gone through infinite suffering.

you sound like Zathras :)

[jadedgnome]

i did :$ ln -s /usr/bin/nodejs /usr/bin/node

[rzr]

sudo ln -fs /usr/bin/nodejs /usr/local/bin/node

[eiger3970]

Yes, digitalmediums' answer fixed it.
"ln -s /usr/bin/nodejs /usr/bin/node"
Muchos gracias 👍

[romerobrjp]

digitalmediums,
That was useful, thanks a lot!

[ghost]

Thank you, it worked for me!

[dunglehome]

@digitalmediums you are right till now. thank you!
"if you install from a package manager you bin may be called nodejs so you just need to symlink it like so "ln -s /usr/bin/nodejs /usr/bin/node""

[chrissilkey]

Great!, thanks for the post

[mattbrosenberg]

Symlink worked great for Debian deploy, thanks!

[CruiseDevice]

sudo apt-get install nodejs-legacy
worked :) 👍

[ghost]

sudo apt-get install nodejs-legacy worked :)

[fgesora]

Some Linux distributions installs NodeJS as nodejs and not node. Simply create a link as
ln -s /usr/bin/nodejs /usr/bin/node

[iranalves85]

thanks, my npm is working now.

[theblackhole]

@fgesora 's solution works for me, thanks 👍 (I use nvm)

[thfontaine]

Thanks, worked for me =)

[alexanderbezverhni]

Thanks @digitalmediums

[aeolusheath]

thanks @digitalmediums

[wellington1993]

thanks @digitalmediums

[matheushf]

dude, thanks! @digitalmediums

[iamtodor]

@digitalmediums you are the great guy! This shitty issue still happens almost 4 yeah later.. (:

[arachchi]

thanks for the help

[curly-hub]

I expected them to fix it after 3 years....

[rpulijala]

Wow, this issue has been since last 4 years... well thats interesting

[Li-ReDBox]

I found this amazing and shocking. Really lack of caring.

[bnoordhuis]

For people coming here through search engines, the correct solution is #3911 (comment) or #3911 (comment).

To the last three commenters: If you are unhappy that Debian decided to call the binary nodejs instead of node, complain to Debian. Griping about it here won't help.

Locking.