browserify error /usr/bin/env: node: No such file or directory browserify error /usr/bin/env: node: No such file or directory javascript javascript

browserify error /usr/bin/env: node: No such file or directory


Some linux distributions install nodejs not as "node" executable but as "nodejs".

In this case you have to manually link to "node" as many packages are programmed after the "node" binary. Something similar also occurs with "python2" not linked to "python".

In this case you can do an easy symlink. For linux distributions which install package binaries to /usr/bin you can do

ln -s /usr/bin/nodejs /usr/bin/node


New Answer:

  1. Uninstall any nodejs package you've installed via your system package manager (dnf, apt-get, etc), delete any silly symlinks you've been recreating every upgrade (lol).
  2. Install NVM,
  3. use nvm to install nodejs: nvm install 6

Old Answer:

Any talk of creating symlinks or installing some other node-package are spurious and not sustainable.

The correct way to solve this is to :

  1. simple install the nodejs package with apt-get like you already have
  2. use update-alternatives to indicate your nodejs binary is responsible for #!/usr/bin/env node

Like so :

sudo apt-get install nodejssudo update-alternatives --install /usr/bin/node nodejs /usr/bin/nodejs 100

This now becomes sustainable throughout package upgrades, dist-upgrades and so forth.


Run apt-get install nodejs-legacy.

Certain linux distributions have changed node.js binary name making it uncompatible with a lot of node.js packages. Package nodejs-legacy provides a symlink to resolve this.