Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"forever command not found" in spite of installed globally #765

raisonde opened this Issue Sep 29, 2015 · 7 comments


None yet
7 participants
Copy link

raisonde commented Sep 29, 2015

I did both
npm install -g forever
npm install forever -g

in rood user

I received below

npm install -g forever

npm WARN optional dep failed, continuing fsevents@1.0.0
/usr/local/nodejs/v0.10.31/bin/forever -> /usr/local/nodejs/v0.10.31/lib/node_modules/forever/bin/forever
forever@0.15.1 /usr/local/nodejs/v0.10.31/lib/node_modules/forever
├── path-is-absolute@1.0.0
├── object-assign@3.0.0
├── colors@0.6.2
├── clone@1.0.2
├── timespan@2.3.0
├── optimist@0.6.1 (wordwrap@0.0.3, minimist@0.0.10)
├── nssocket@0.5.3 (eventemitter2@0.4.14, lazy@1.0.11)
├── shush@1.0.0 (strip-json-comments@0.1.3, caller@0.0.1)
├── cliff@0.1.10 (eyes@0.1.8, colors@1.0.3)
├── winston@0.8.3 (cycle@1.0.3, stack-trace@0.0.9, eyes@0.1.8, isstream@0.1.2, async@0.2.10, pkginfo@0.3.0)
├── utile@0.2.1 (deep-equal@1.0.1, ncp@0.4.2, async@0.2.10, i@0.3.3, mkdirp@0.5.1, rimraf@2.4.3)
├── nconf@0.6.9 (ini@1.3.4, async@0.2.9, optimist@0.6.0)
├── prettyjson@1.1.3 (colors@1.1.2, minimist@1.2.0)
├── flatiron@0.4.3 (optimist@0.6.0, director@1.2.7, prompt@0.2.14, broadway@0.3.6)
└── forever-monitor@1.6.0 (minimatch@2.0.10, ps-tree@0.0.3, chokidar@1.1.0, broadway@0.3.6)


This comment has been minimized.

Copy link

indexzero commented Sep 29, 2015

Looks like it worked. Make sure it's in your PATH

@indexzero indexzero closed this Sep 29, 2015


This comment has been minimized.

Copy link

raisonde commented Oct 1, 2015

Should I add path manually? I confirmed there's no forever's path in my $path, and I know adding path(/usr/local/nodejs/v0.10.31/lib/node_modules/forever/bin) can solve this problem. But I thought path would added automatically when I installed globally.
Am I know wrong?


This comment has been minimized.

Copy link

tehg00se commented Dec 31, 2016

thats my nigga


This comment has been minimized.

Copy link

NextZeus commented Mar 31, 2017

this issue should not be closed, i met this issue today . please give us a official resolution 。


This comment has been minimized.

Copy link

harshitparmar commented Oct 31, 2017

Hello everyone. I've a solution on this. You can checkout the article at my Support Portal. Also if you need more asst. do contact me via email and I'll try my best to help you !


This comment has been minimized.

Copy link

Dmdv commented Aug 7, 2018

The same issue.
Users should not add to the PATH manually.
It's not usable at all on remote server.

  1. run npm get prefix
    in my case this will be /usr/local/Cellar/node/9.11.1

  2. open ~/.bash_profile or any other profile file specific to OS
    and add the prefix to the path:
    export PATH="$PATH:/usr/local/Cellar/node/9.11.1/bin"

  3. save, close and run
    source ~/.bash_profile


This comment has been minimized.

Copy link

ElectronHarvester commented Nov 9, 2018

@Dmdv You are the hero we needed. Followed this and now I'm up and running! For those coming from aws ec2 your bash_profile might look like:

#User specific environment and startup programs


export PATH

You will need to restart your terminal to enable the commands at this point

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.