indexzero/forever — Issue #138: Cannot find module winston / 
Author: balthasar
Created: 2011-10-13 15:29:50+00:00
State: open

Hi,

I have node.js up and running with phantomjs. I can run node easily with
`xvfb-run node server.js`
I have installed forever with the npm
`npm install forever`
but when I try run forever [anything] i get the below error

$ forever list

node.js:134
throw e; // process.nextTick error, or 'error' event on first tick
^
Error: Cannot find module 'winston'
at Function._resolveFilename (module.js:317:11)
at Function._load (module.js:262:25)
at require (module.js:346:19)
at Object. (/home/ubuntu/local/bin/forever:5:15)
at Module._compile (module.js:402:26)
at Object..js (module.js:408:10)
at Module.load (module.js:334:31)
at Function._load (module.js:293:12)
at Array. (module.js:421:10)
at EventEmitter._tickCallback (node.js:126:26)

I have read other issues listed and then installed winston with the npm
`npm install winston`

However I now get the following error.

$ forever list
node.js:134
throw e; // process.nextTick error, or 'error' event on first tick
^
Error: Cannot find module './../lib/forever'
at Function._resolveFilename (module.js:317:11)
at Function._load (module.js:262:25)
at require (module.js:346:19)
at Object. (/home/ubuntu/local/bin/forever:7:15)
at Module._compile (module.js:402:26)
at Object..js (module.js:408:10)
at Module.load (module.js:334:31)
at Function._load (module.js:293:12)
at Array. (module.js:421:10)
at EventEmitter._tickCallback (node.js:126:26)

Below is `npm ls` with winstno installed

$ npm ls
npm WARN seq >=0.1.7 Unmet dependency in /home/ubuntu/node_modules/phantom/node_ modules/browserify/node_modules/detective/node_modules/findit
/home/ubuntu
âââ¬ forever@0.7.1
â âââ async@0.1.10
â âââ cliff@0.1.5
â âââ¬ clip@0.1.6
â â âââ¬ prompt@0.1.9
â â â âââ¬ winston@0.5.5
â â â âââ¬ loggly@0.3.9
â â â â âââ request@2.1.1
â â â âââ stack-trace@0.0.6
â â âââ reconf@0.1.1
â â âââ¬ winston@0.3.5
â â âââ¬ loggly@0.3.9
â â âââ request@2.1.1
â âââ colors@0.5.1
â âââ daemon@0.3.2
â âââ¬ dnode@0.8.2
â â âââ dnode-protocol@0.0.12
â â âââ lazy@1.0.7
â â âââ socket.io@0.6.18
â â âââ traverse@0.4.6
â âââ eyes@0.1.6
â âââ¬ minimatch@0.0.4
â â âââ lru-cache@1.0.4
â âââ mkdirp@0.0.7
â âââ¬ nconf@0.4.3
â â âââ ini@1.0.1
â âââ¬ optimist@0.2.6
â â âââ wordwrap@0.0.2
â âââ pkginfo@0.2.2
â âââ portfinder@0.2.0
â âââ¬ ps-tree@0.0.0
â â âââ event-stream@0.5.1
â âââ timespan@2.0.1
â âââ watch@0.3.3
â âââ¬ winston@0.5.5
â âââ¬ loggly@0.3.9
â â âââ request@2.1.1
â âââ stack-trace@0.0.6
âââ jQuery@1.6.3
âââ¬ jsdom@0.2.4
â âââ contextify@0.0.6
â âââ cssom@0.2.0
â âââ htmlparser@1.7.3
â âââ request@2.1.1
âââ¬ phantom@0.1.0
â âââ¬ browserify@1.5.0
â â âââ coffee-script@1.1.2
â â âââ commondir@0.0.0
â â âââ¬ detective@0.0.3
â â â âââ¬ burrito@0.2.10
â â â â âââ traverse@0.5.1
â â â â âââ uglify-js@1.0.7
â â â âââ¬ findit@0.1.0 extraneous
â â â âââ UNMET DEPENDENCY seq >=0.1.7
â â âââ nub@0.0.0
â â âââ¬ optimist@0.2.6
â â â âââ wordwrap@0.0.2
â â âââ resolve@0.0.4
â âââ¬ dnode@0.8.2
â â âââ dnode-protocol@0.0.12
â â âââ lazy@1.0.7
â â âââ socket.io@0.6.18
â â âââ traverse@0.4.6
â âââ¬ dnode-protocol@0.1.0
â â âââ traverse@0.5.1
â âââ¬ express@2.4.7
â âââ connect@1.7.1
â âââ mime@1.2.4
â âââ mkdirp@0.0.7
â âââ qs@0.3.1
âââ¬ winston@0.5.5
âââ async@0.1.10
âââ colors@0.5.1
âââ eyes@0.1.6
âââ¬ loggly@0.3.9
â âââ request@2.1.1
â âââ timespan@2.2.0
âââ pkginfo@0.2.2
âââ stack-trace@0.0.6

Could you shed any light on the above.

Thanks