Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

[sudo] npm install -g forever fails on node v0.8.0 #302

Closed
vincentmac opened this Issue · 10 comments

6 participants

@vincentmac

Just installed node v0.8.0 (includes npm v1.1.32) and am having an issue updating/reinstalling forever. Looks like it has something to do with node-fork?

λ|enlightenment ~: sudo npm install -g forever                                                     
zsh: correct 'forever' to '.forever' [nyae]? n
npm http GET https://registry.npmjs.org/forever
npm http 304 https://registry.npmjs.org/forever
npm http GET https://registry.npmjs.org/broadway
npm http GET https://registry.npmjs.org/cliff
npm http GET https://registry.npmjs.org/daemon
npm http GET https://registry.npmjs.org/flatiron
npm http GET https://registry.npmjs.org/microtime
npm http GET https://registry.npmjs.org/minimatch
npm http GET https://registry.npmjs.org/node-fork
npm http GET https://registry.npmjs.org/pkginfo
npm http GET https://registry.npmjs.org/nconf
npm http GET https://registry.npmjs.org/nssocket
npm http GET https://registry.npmjs.org/optimist
npm http GET https://registry.npmjs.org/portfinder
npm http GET https://registry.npmjs.org/ps-tree
npm http GET https://registry.npmjs.org/timespan
npm http GET https://registry.npmjs.org/watch
npm http GET https://registry.npmjs.org/utile
npm http GET https://registry.npmjs.org/winston
npm http 304 https://registry.npmjs.org/broadway
npm http 304 https://registry.npmjs.org/cliff
npm http 304 https://registry.npmjs.org/daemon
npm http 304 https://registry.npmjs.org/flatiron
npm http 304 https://registry.npmjs.org/microtime
npm http 304 https://registry.npmjs.org/minimatch
npm http 304 https://registry.npmjs.org/node-fork
npm http 304 https://registry.npmjs.org/pkginfo
npm ERR! Error: No compatible version found: node-fork@'>=0.4.0- <0.5.0-'
npm ERR! No valid targets found.
npm ERR! Perhaps not compatible with your version of node?
npm ERR!     at installTargetsError (/usr/local/lib/node_modules/npm/lib/cache.js:506:10)
npm ERR!     at next_ (/usr/local/lib/node_modules/npm/lib/cache.js:452:17)
npm ERR!     at next (/usr/local/lib/node_modules/npm/lib/cache.js:427:44)
npm ERR!     at /usr/local/lib/node_modules/npm/lib/cache.js:419:5
npm ERR!     at saved (/usr/local/lib/node_modules/npm/node_modules/npm-registry-client/lib/get.js:136:7)
npm ERR!     at /usr/local/lib/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:230:7
npm ERR!     at Object.oncomplete (fs.js:297:15)
npm ERR!  [Error: No compatible version found: node-fork@'>=0.4.0- <0.5.0-'
npm ERR! No valid targets found.
npm ERR! Perhaps not compatible with your version of node?]
npm ERR! You may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

npm ERR! System Darwin 11.4.0
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "forever"
npm ERR! cwd /Users/vincent
npm ERR! node -v v0.8.0
npm ERR! npm -v 1.1.32
npm ERR! message No compatible version found: node-fork@'>=0.4.0- <0.5.0-'
npm ERR! message No valid targets found.
npm ERR! message Perhaps not compatible with your version of node?
npm http 304 https://registry.npmjs.org/nconf
npm http 304 https://registry.npmjs.org/nssocket
npm http 304 https://registry.npmjs.org/optimist
npm http 304 https://registry.npmjs.org/portfinder
npm http 304 https://registry.npmjs.org/ps-tree
npm http 304 https://registry.npmjs.org/timespan
npm http 304 https://registry.npmjs.org/utile
npm http 304 https://registry.npmjs.org/watch
npm http 304 https://registry.npmjs.org/winston
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/vincent/npm-debug.log
npm ERR! not ok code 0
@dstroot

Same issue...

@dhruv-bhatia

Same thing here (Ubuntu 12.04 LTS)

@ikr

Same here. OSX, node 0.8.0 installed via homebrew

@gvsmirnov

Same issue on debian squeeze.

@AvianFlu

This failure is because of the engines field in the package.json of node-fork. Any error like this will go away with npm install --force.

With that said, forever@0.9.2 doesn't work properly on 0.8 - we've been focused on refactoring forever to take advantage of new core features, and a new version will be available for testing (as a branch of this repo) starting later today or tomorrow.

I apologize for the inconvenience, but this refactor is going to be a drastic improvement in several areas, and so it has taken precedence over fixing bugs in compiled addons that we don't plan to continue using.

@vincentmac

No problem. Thanks for the update.

@AvianFlu

Please test the node-0.8 branch:

git clone https://github.com/nodejitsu/forever
cd forever
git checkout node-0.8
sudo npm link .

All the tests are passing on linux and darwin - please let me know if I broke anyone's use case.

@vincentmac

The commands you listed above execute without error; however, when I try to use forever to test a project I get the following:

λ|enlightenment workspace/invoice: which forever                                      ± modular -!?
/usr/local/bin/forever
λ|enlightenment workspace/invoice: forever start app.js                               ± modular -!?

module.js:340
    throw err;
          ^
Error: Cannot find module '/Users/vincent/workspace/forever'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Module.require (module.js:362:17)
    at require (module.js:378:17)
    at Object.<anonymous> (/Users/vincent/github/forever/lib/forever/worker.js:6:15)
    at Module._compile (module.js:449:26)
    at Object.Module._extensions..js (module.js:467:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:362:17)
@AvianFlu

I just made a commit that should fix this - let me know if it doesn't.

@vincentmac

That fixed it. Thanks for the quick response on getting forever running with node v0.8.

I'll mark this as closed.

@vincentmac vincentmac closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.