Browserify command not found

Question

Quick question, when I run browserify index.js -o app.js from mac terminal, I get command not found. I have done npm install -g browserify but still no luck. Any idea why I am getting this?

Thank you

It was easier for me to do a gist than to paste here: https://gist.github.com/pertrai1/4ccf77e7b31cb5628b5d

can you paste the console log when you rerun `npm install -g browserify`? — Mike 'Pomax' Kamermans, Jul 25 '14 at 02:53
So you should have a binding `/Users/robsimpson/npm/bin/browserify -> /Users/robsimpson/npm/lib/node_modules/browserify/bin/cmd.js` now. Does `/Users/robsimpson/npm/bin/browserify` work when you try to run it? — Mike 'Pomax' Kamermans, Jul 25 '14 at 03:12

prosti · Answer 1 · 2016-09-23T10:15:12.570

16

Just install it in a global space like this if you need to run it from the command line.

npm install browserify -g

You may need to run

npm uninstall browserify -g fist just to be sure you don't have false aliases.

edited Sep 23 '16 at 10:15

answered Sep 23 '16 at 10:09

prosti

35,325
9
162
139

This is necessary but not sufficient, since that will still not add the command to your PATH. See my answer. – jjpe Sep 23 '16 at 10:13
I see, sorry, I was not reading the whole thread, but this must work, eventually. – prosti Sep 23 '16 at 10:16
No need for apologies, nobody can know everything :) – jjpe Sep 23 '16 at 10:18
Worked for me, since it's often used globally I forgot to put it in my `dev-dependencies` – Jesse Reza Khorasanee Nov 13 '19 at 23:47

jjpe · Answer 2 · 2016-10-12T20:42:14.403

7

Add this to your ~/.bashrc or equivalent:

export PATH=$PATH:~/.npm-global/bin/

Then, to actually have this take effect in your terminal session, execute source ~/.bashrc.

At this point you can execute browserify, as well as potentially many other commands. Check out ~/.npm-global/bin/ to see what's become available.

edited Oct 12 '16 at 20:42

answered Sep 23 '16 at 10:16

jjpe

654
4
13

score 1 · Answer 3 · edited Sep 16 '15 at 14:07

1

I could not get browserify to work either.

Running ~/.npm/bin/browserify does work.

Other packages seem to run fine (phantomjs for instance).

A workaround fix seems to be adding alias browserify='~/.npm/bin/browserify' to your .bash_profile

edited Sep 16 '15 at 14:07

Mogsdad

42,835
20
145
262

answered Sep 16 '15 at 14:03

Janvdm

11
1

score 0 · Answer 4 · answered May 25 '18 at 22:35

If for some reason the browserify command has not been installed at all (can happen for example if you're running Homebrew on old unsupported Mac OS X versions), an alternative is to call it via node, for example:

export NODE_PATH=/usr/local/share/npm/lib/node_modules
node -e 'require("browserify")("input.js").bundle().pipe(fs.createWriteStream("output.js"))'

score 0 · Answer 5 · answered Nov 17 '19 at 10:53

0

It is an old post but I believe people are still facing the same problem, like me.

This was how I solved my problem:

<your project folder>/node_modules/browserify/bin/cmd.js main.js -o bundle.js

answered Nov 17 '19 at 10:53

VeryNiceArgumentException

1,628
1
18
29

score 0 · Answer 6 · answered May 17 '20 at 14:50

0

As a Mac user I had to add

export PATH=$PATH:/usr/local/Cellar/node/13.6.0/bin/

in ~.bash_profile

Why Cellar path i dont know.

answered May 17 '20 at 14:50

luky

2,057
3
18
31

Browserify command not found

6 Answers6

Linked