When I run npm install node-inspector, I get the following:
....
GET https://registry.npmjs.org/policyfile/0.0.4
npm http GET https://registry.npmjs.org/mime
npm http GET https://registry.npmjs.org/qs
npm http GET https://registry.npmjs.org/formidable
npm http 304 https://registry.npmjs.org/socket.io-client/0.9.8
npm http 304 https://registry.npmjs.org/redis/0.7.2
npm http 304 https://registry.npmjs.org/policyfile/0.0.4
npm http 304 https://registry.npmjs.org/formidable
npm http 304 https://registry.npmjs.org/mime
npm http 304 https://registry.npmjs.org/qs
npm http GET https://registry.npmjs.org/hiredis
npm http GET https://registry.npmjs.org/uglify-js/1.2.5
npm http GET https://registry.npmjs.org/active-x-obfuscator/0.0.1
npm http GET https://registry.npmjs.org/xmlhttprequest/1.2.2
npm http GET https://registry.npmjs.org/ws
npm http 304 https://registry.npmjs.org/hiredis
> hiredis#0.1.14 preinstall C:\apache\expTest\node_modules\node-inspector\node_modules\socket.io\node_modules\redis\node_modules\hiredis
> make || gmake
npm http 304 https://registry.npmjs.org/uglify-js/1.2.5
npm http 304 https://registry.npmjs.org/ws
npm http 304 https://registry.npmjs.org/active-x-obfuscator/0.0.1
npm http 304 https://registry.npmjs.org/xmlhttprequest/1.2.2
'make' is not recognized as an internal or external command,
operable program or batch file.
'gmake' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! error installing hiredis#0.1.14
npm ERR! error installing redis#0.7.2
npm ERR! error installing socket.io#0.9.8
npm ERR! error rolling back socket.io#0.9.8 Error: UNKNOWN, unknown error 'C:\apache\expTest\node_modules\node-inspector\node_modules\socket.io\node_modules\socket.io-client'
npm ERR! error installing node-inspector#0.2.0beta3
npm ERR! Error: ENOENT, no such file or directory 'C:\apache\expTest\node_modules\node-inspector\node_modules\socket.io\node_modules\socket.io-client\node_modules\___ws.npm\p
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!
npm ERR! System Windows_NT 6.1.7601
npm ERR! command "c:\\Program Files (x86)\\nodejs\\\\node.exe" "c:\\Program Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "node-inspector"
npm ERR! cwd C:\apache\expTest
npm ERR! node -v v0.6.11
npm ERR! npm -v 1.1.1
npm ERR! path C:\apache\expTest\node_modules\node-inspector\node_modules\socket.io\node_modules\socket.io-client\node_modules\___ws.npm\package\lib\Validation.fallback.js
npm ERR! fstream_path C:\apache\expTest\node_modules\node-inspector\node_modules\socket.io\node_modules\socket.io-client\node_modules\___ws.npm\package\lib\Validation.fallbac
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! message ENOENT, no such file or directory 'C:\apache\expTest\node_modules\node-inspector\node_modules\socket.io\node_modules\socket.io-client\node_modules\___ws.npm\
npm ERR! errno {}
npm ERR! fstream_stack Object.oncomplete (c:\Program Files (x86)\nodejs\node_modules\npm\node_modules\fstream\lib\writer.js:204:26)
npm ERR! error rolling back node-inspector#0.2.0beta3 Error: UNKNOWN, unknown error 'C:\apache\expTest\node_modules\node-inspector\node_modules\socket.io\node_modules\socket.
npm ERR! hiredis#0.1.14 preinstall: `make || gmake`
npm ERR! `cmd "/c" "make || gmake"` failed with 1
npm ERR!
npm ERR! Failed at the hiredis#0.1.14 preinstall script.
npm ERR! This is most likely a problem with the hiredis package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! make || gmake
npm ERR! You can get their info via:
npm ERR! npm owner ls hiredis
npm ERR! There is likely additional logging output above.
npm ERR!
npm ERR! System Windows_NT 6.1.7601
npm ERR! command "c:\\Program Files (x86)\\nodejs\\\\node.exe" "c:\\Program Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "node-inspector"
npm ERR! cwd C:\apache\expTest
npm ERR! node -v v0.6.11
npm ERR! npm -v 1.1.1
npm ERR! code ELIFECYCLE
npm ERR! message hiredis#0.1.14 preinstall: `make || gmake`
npm ERR! message `cmd "/c" "make || gmake"` failed with 1
npm ERR! errno {}
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! C:\apache\expTest\npm-debug.log
npm not ok
It looks like it is trying to run a nix command at hiredis, which fails, crashing the entire install. Is there any way to get around this? I have heard plenty of Windows users using node-inspector, but perhaps this is a dependency from a newer version. Any ideas?
As M. Laing said, you're missing GNU make, which is required by hiredis (a redis connector).
You don't need redis for node-inspector, but it's required by socket.io, even though it's for a completely optional feature. I've opened an issue on github about that:
https://github.com/LearnBoost/socket.io/issues/978
While this gets resolved, here's a work around:
Download socket.io's ZIP archive from github and unzip it.
Edit the package.json file and remove redis from the dependencies.
Run a cmd, enter the folder and type npm install.
Type npm install node-inspector again.
Since socket.io is now installed, it should now succeed.
Related
I am trying to install ari-client,using this command:
sudo npm install ari-client
Here is the error I get:
npm http GET http://registry.npmjs.org/ari-client
npm http 304 http://registry.npmjs.org/ari-client
npm http GET http://registry.npmjs.org/swagger-client/2.0.26
npm http GET http://registry.npmjs.org/ws/0.4.31
npm http GET http://registry.npmjs.org/underscore/1.6.0
npm http GET https://registry.npmjs.org/node-uuid/-/node-uuid-1.4.1.tgz
npm http 400 https://registry.npmjs.org/node-uuid/-/node-uuid-1.4.1.tgz
npm ERR! fetch failed https://registry.npmjs.org/node-uuid/-/node-uuid-1.4.1.tgz
npm ERR! Error: 400 Bad Request
npm ERR! at WriteStream.<anonymous> (/usr/share/npm/lib/utils/fetch.js:57:12)
npm ERR! at WriteStream.EventEmitter.emit (events.js:117:20)
npm ERR! at fs.js:1601:14
npm ERR! at /usr/lib/nodejs/graceful-fs/graceful-fs.js:103:5
npm ERR! at Object.oncomplete (fs.js:107:15)
npm ERR! If you need help, you may report this log at:
npm ERR! <http://bugs.debian.org/npm>
npm ERR! or use
npm ERR! reportbug --attach /home/bzegeju/npm-debug.log npm
npm ERR! System Linux 3.11.0-26-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install" "ari-client"
npm ERR! cwd /home/bzegeju
npm ERR! node -v v0.10.15
npm ERR! npm -v 1.2.18
npm http 304 http://registry.npmjs.org/ws/0.4.31
npm http 304 http://registry.npmjs.org/underscore/1.6.0
npm http 304 http://registry.npmjs.org/swagger-client/2.0.26
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/bzegeju/npm-debug.log
npm ERR! not ok code 0
Any help on the error or how I can manually install the library?
For Manual installation:
1.Go to npm site search for "ari-client".
2.Click the given "github" link , from there you can download as ZIP file.
3.Extract it and use in your project
Versions
Linux distro and version: Raspbian GNU/Linux 7 (wheezy)"
Python: 2.7.3
Nodejs: v0.10.22
NPM: 1.3.15
Every time I try to install forever globally on my Raspberry pi it fails. The error is listed below.
sudo npm install forever -g
npm http GET https://registry.npmjs.org/forever
npm http 304 https://registry.npmjs.org/forever
npm http GET https://registry.npmjs.org/utile/0.1.7
npm http GET https://registry.npmjs.org/winston/0.7.1
npm http GET https://registry.npmjs.org/colors/0.6.0-1
npm http GET https://registry.npmjs.org/cliff/0.1.8
npm http GET https://registry.npmjs.org/flatiron/0.3.5
npm http GET https://registry.npmjs.org/forever-monitor/1.2.3
npm http GET https://registry.npmjs.org/nconf/0.6.7
npm http GET https://registry.npmjs.org/nssocket
npm http GET https://registry.npmjs.org/optimist/0.4.0
npm http GET https://registry.npmjs.org/pkginfo/0.3.0
npm http GET https://registry.npmjs.org/timespan/2.0.1
npm http GET https://registry.npmjs.org/watch/0.7.0
npm http 304 https://registry.npmjs.org/utile/0.1.7
npm http 304 https://registry.npmjs.org/cliff/0.1.8
npm http 304 https://registry.npmjs.org/winston/0.7.1
npm http 304 https://registry.npmjs.org/colors/0.6.0-1
npm http 304 https://registry.npmjs.org/forever-monitor/1.2.3
npm http 304 https://registry.npmjs.org/nconf/0.6.7
npm http 304 https://registry.npmjs.org/nssocket
npm http 304 https://registry.npmjs.org/optimist/0.4.0
npm http 304 https://registry.npmjs.org/flatiron/0.3.5
npm http 304 https://registry.npmjs.org/pkginfo/0.3.0
npm http 304 https://registry.npmjs.org/timespan/2.0.1
npm http 304 https://registry.npmjs.org/watch/0.7.0
npm http GET https://registry.npmjs.org/eventemitter2
npm http GET https://registry.npmjs.org/lazy
npm http GET https://registry.npmjs.org/async
npm http GET https://registry.npmjs.org/deep-equal
npm http GET https://registry.npmjs.org/i
npm http GET https://registry.npmjs.org/mkdirp
npm http GET https://registry.npmjs.org/ncp
npm http GET https://registry.npmjs.org/rimraf
npm http 304 https://registry.npmjs.org/lazy
npm http 304 https://registry.npmjs.org/eventemitter2
npm http 304 https://registry.npmjs.org/mkdirp
npm http 304 https://registry.npmjs.org/ncp
npm http 304 https://registry.npmjs.org/rimraf
npm http 304 https://registry.npmjs.org/async
npm http 304 https://registry.npmjs.org/deep-equal
npm http 304 https://registry.npmjs.org/i
npm http GET https://registry.npmjs.org/wordwrap
npm http 304 https://registry.npmjs.org/wordwrap
npm http GET https://registry.npmjs.org/broadway
npm http GET https://registry.npmjs.org/minimatch
npm http GET https://registry.npmjs.org/ps-tree
npm http GET https://registry.npmjs.org/watch
npm http GET https://registry.npmjs.org/broadway/0.2.7
npm http GET https://registry.npmjs.org/optimist/0.3.5
npm http GET https://registry.npmjs.org/prompt/0.2.9
npm http GET https://registry.npmjs.org/director/1.1.10
npm http 304 https://registry.npmjs.org/minimatch
npm http 304 https://registry.npmjs.org/broadway
npm http 304 https://registry.npmjs.org/watch
npm http 304 https://registry.npmjs.org/broadway/0.2.7
npm http 304 https://registry.npmjs.org/optimist/0.3.5
npm http 304 https://registry.npmjs.org/prompt/0.2.9
npm http 304 https://registry.npmjs.org/director/1.1.10
npm http 304 https://registry.npmjs.org/ps-tree
npm ERR! Error: ENOENT, open '/usr/local/lib/node_modules/forever/node_modules/cliff/examples/put-rows-colors.js'
npm ERR! If you need help, 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 Linux 3.6.11+
npm ERR! command "node" "/usr/local/bin/npm" "install" "forever" "-g"
npm ERR! cwd /home/pi
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.15
npm ERR! path /usr/local/lib/node_modules/forever/node_modules/cliff/examples/put-rows-colors.js
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! Error: ENOENT, lstat '/usr/local/lib/node_modules/forever/node_modules/winston/test/log-rewriter-test.js'
npm ERR! If you need help, 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 Linux 3.6.11+
npm ERR! command "node" "/usr/local/bin/npm" "install" "forever" "-g"
npm ERR! cwd /home/pi
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.15
npm ERR! path /usr/local/lib/node_modules/forever/node_modules/winston/test/log-rewriter-test.js
npm ERR! fstream_path /usr/local/lib/node_modules/forever/node_modules/winston/test/log-rewriter-test.js
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack /usr/local/lib/node_modules/npm/node_modules/fstream/lib/writer.js:284:26
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR! Error: ENOENT, lstat '/usr/local/lib/node_modules/forever/node_modules/nssocket/node_modules/lazy/test/lines.js'
npm ERR! If you need help, 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 Linux 3.6.11+
npm ERR! command "node" "/usr/local/bin/npm" "install" "forever" "-g"
npm ERR! cwd /home/pi
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.15
npm ERR! path /usr/local/lib/node_modules/forever/node_modules/nssocket/node_modules/lazy/test/lines.js
npm ERR! fstream_path /usr/local/lib/node_modules/forever/node_modules/nssocket/node_modules/lazy/test/lines.js
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! fstream_stack /usr/local/lib/node_modules/npm/node_modules/fstream/lib/writer.js:284:26
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR! EEXIST, mkdir '/usr/local/lib/node_modules/forever/node_modules/nconf/lib/nconf/stores'
File exists: /usr/local/lib/node_modules/forever/node_modules/nconf/lib/nconf/stores
Move it away, and try again.
npm ERR! System Linux 3.6.11+
npm ERR! command "node" "/usr/local/bin/npm" "install" "forever" "-g"
npm ERR! cwd /home/pi
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.15
npm ERR! path /usr/local/lib/node_modules/forever/node_modules/nconf/lib/nconf/stores
npm ERR! fstream_path /usr/local/lib/node_modules/forever/node_modules/nconf/lib/nconf/stores/file.js
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code EEXIST
npm ERR! errno 47
npm ERR! fstream_stack /usr/local/lib/node_modules/npm/node_modules/fstream/lib/writer.js:171:23
npm ERR! fstream_stack /usr/local/lib/node_modules/npm/node_modules/mkdirp/index.js:37:53
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR! Failed to parse json
npm ERR! Unexpected end of input
npm ERR! File: /root/.npm/broadway/0.2.7/package/package.json
npm ERR! Failed to parse package.json data.
npm ERR! package.json must be actual JSON, not just JavaScript.
npm ERR!
npm ERR! This is not a bug in npm.
npm ERR! Tell the package author to fix their package.json file. JSON.parse
npm ERR! System Linux 3.6.11+
npm ERR! command "node" "/usr/local/bin/npm" "install" "forever" "-g"
npm ERR! cwd /home/pi
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.15
npm ERR! file /root/.npm/broadway/0.2.7/package/package.json
npm ERR! code EJSONPARSE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/pi/npm-debug.log
npm ERR! not ok code 0
similarly if I try to do this without sudo, I get the following:
npm install forever -g
npm http GET https://registry.npmjs.org/forever
npm http 304 https://registry.npmjs.org/forever
npm ERR! error rolling back Error: EACCES, unlink '/usr/local/lib/node_modules/forever'
npm ERR! error rolling back forever#0.10.9 { [Error: EACCES, unlink '/usr/local/lib/node_modules/forever']
npm ERR! error rolling back errno: 3,
npm ERR! error rolling back code: 'EACCES',
npm ERR! error rolling back path: '/usr/local/lib/node_modules/forever' }
npm ERR! Error: EACCES, unlink '/usr/local/lib/node_modules/forever'
npm ERR! { [Error: EACCES, unlink '/usr/local/lib/node_modules/forever']
npm ERR! errno: 3,
npm ERR! code: 'EACCES',
npm ERR! path: '/usr/local/lib/node_modules/forever' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
npm ERR! System Linux 3.6.11+
npm ERR! command "node" "/usr/local/bin/npm" "install" "forever" "-g"
npm ERR! cwd /home/pi
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.15
npm ERR! path /usr/local/lib/node_modules/forever
npm ERR! code EACCES
npm ERR! errno 3
npm ERR! stack Error: EACCES, unlink '/usr/local/lib/node_modules/forever'
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/pi/npm-debug.log
npm ERR! not ok code 0
Try installing node with nvm. This installs node in your home directory so sudo permissions are not required for installing global modules.
It looks like the module you are installing is having issues with relative directories and it could help with not using sudo.
Paths specified with a . are relative to the current working directory, not relative to the script file. So the file might be found if you run node app.js but not if you run node folder/app.js.
To make a path relative to the script, you must use the __dirname variable.
__dirname + '/path/to/file'
Src
I am following the testatcular vide tutorial http://vojtajina.github.com/testacular/.
I installed nodejs and when I tried to install testacular with
sudo npm install -g testacular
I get this error :
npm http GET https://registry.npmjs.org/testacular
npm http 304 https://registry.npmjs.org/testacular
npm http GET https://registry.npmjs.org/chokidar
npm http GET https://registry.npmjs.org/minimatch
npm http GET https://registry.npmjs.org/socket.io
npm http GET https://registry.npmjs.org/glob
npm http GET https://registry.npmjs.org/optimist
npm http 304 https://registry.npmjs.org/glob
npm http 304 https://registry.npmjs.org/socket.io
npm http 304 https://registry.npmjs.org/optimist
npm http 304 https://registry.npmjs.org/chokidar
npm http 304 https://registry.npmjs.org/minimatch
> chokidar#0.4.0 postinstall /usr/local/lib/node_modules/testacular/node_modules/chokidar
> node setup.js postinstall
npm ERR! error installing chokidar#0.4.0
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
npm WARN /usr/share/doc/nodejs/README.Debian
npm WARN
npm ERR! error installing testacular#0.0.17
npm ERR! Error: ENOENT, lstat '/usr/local/lib/node_modules/testacular/node_modules/___minimatch.npm/package/minimatch.js'
npm ERR! You may report this log at:
npm ERR! <http://bugs.debian.org/npm>
npm ERR! or use
npm ERR! reportbug --attach /home/adio/workspace/java/tutorial/angularJS/npm-debug.log npm
npm ERR!
npm ERR! System Linux 3.5.0-17-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install" "-g" "testacular"
npm ERR! cwd /home/adio/workspace/java/tutorial/angularJS
npm ERR! node -v v0.6.19
npm ERR! npm -v 1.1.4
npm ERR! path /usr/local/lib/node_modules/testacular/node_modules/___minimatch.npm/package/minimatch.js
npm ERR! fstream_path /usr/local/lib/node_modules/testacular/node_modules/___minimatch.npm/package/minimatch.js
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! message ENOENT, lstat '/usr/local/lib/node_modules/testacular/node_modules/___minimatch.npm/package/minimatch.js'
npm ERR! errno {}
npm ERR! fstream_stack Object.oncomplete (/usr/lib/nodejs/fstream/lib/writer.js:204:26)
npm ERR! error rolling back testacular#0.0.17 Error: ENOTEMPTY, rmdir '/usr/local/lib/node_modules/testacular/node_modules/___glob.npm/package/test'
npm ERR! chokidar#0.4.0 postinstall: `node setup.js postinstall`
npm ERR! `sh "-c" "node setup.js postinstall"` failed with 1
npm ERR!
npm ERR! Failed at the chokidar#0.4.0 postinstall script.
npm ERR! This is most likely a problem with the chokidar package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node setup.js postinstall
npm ERR! You can get their info via:
npm ERR! npm owner ls chokidar
npm ERR! There is likely additional logging output above.
npm ERR!
npm ERR! System Linux 3.5.0-17-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install" "-g" "testacular"
npm ERR! cwd /home/adio/workspace/java/tutorial/angularJS
npm ERR! node -v v0.6.19
npm ERR! npm -v 1.1.4
npm ERR! code ELIFECYCLE
npm ERR! message chokidar#0.4.0 postinstall: `node setup.js postinstall`
npm ERR! message `sh "-c" "node setup.js postinstall"` failed with 1
npm ERR! errno {}
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/adio/workspace/java/tutorial/angularJS/npm-debug.log
npm not ok
anybody ran into this problem ?
thanks in advance for help.
Let me guess, is it happening on a Win7 machine 64 bits?
I got the same error and it was already reported on testacular github
The only workaround I found was installing node.js 32 bits instead of 64 bits version.
I encourage you to post another comment on their github so maybe it will be reconsidered
The problem was in the versions as the error log suggests. On Ubuntu 12.10 install NodeJS with sudo apt-get install nodejs will result in installing nodejs 0.6, but you need nodejs version 0.8 to install testacular so I followed this tutorial to install nodejs 0.8
http://davidtsadler.com/archives/2012/05/06/installing-node-js-on-ubuntu/
I searched for a long time, but haven't found the right answer yet.
I'm not the only one who has/had problems installing Socket.IO >0.7.7 but other solutions didn't work for me.
A possible problem could be an old version of GNU tar (version is 1.19) but I donĀ“t know how to upgrade it or if it is possible at all.
An Update to a newer version of Ubuntu is not possible for me at this time.
If there is no way to update tar or something similar: Can I install Socket.IO without npm?
Here is the Output of "npm install socket.io":
npm http GET https://registry.npmjs.org/socket.io
npm http 304 https://registry.npmjs.org/socket.io
npm http GET https://registry.npmjs.org/socket.io-client/0.8.7
npm http GET https://registry.npmjs.org/policyfile/0.0.4
npm http GET https://registry.npmjs.org/redis/0.6.7
npm http 304 https://registry.npmjs.org/policyfile/0.0.4
npm http 304 https://registry.npmjs.org/socket.io-client/0.8.7
npm http 304 https://registry.npmjs.org/redis/0.6.7
npm http GET https://registry.npmjs.org/uglify-js/1.0.6
npm http GET https://registry.npmjs.org/websocket-client/1.0.0
npm http GET https://registry.npmjs.org/xmlhttprequest/1.2.2
npm http 304 https://registry.npmjs.org/uglify-js/1.0.6
npm http 304 https://registry.npmjs.org/xmlhttprequest/1.2.2
npm http 304 https://registry.npmjs.org/websocket-client/1.0.0
npm ERR! error installing websocket-client#1.0.0
npm ERR! error installing socket.io-client#0.8.7
npm ERR! Error: ENOENT, no such file or directory '/home/admin/node_modules/socket.io/node_modules/socket.io-client/node_modules/___xmlhttprequest.npm/package/package.json'
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!
npm ERR! System Linux 2.6.32.2-xxxx-grs-ipv6-32
npm ERR! command "node" "/home/admin/local/bin/npm" "install" "socket.io"
npm ERR! cwd /home/admin
npm ERR! node -v v0.6.10
npm ERR! npm -v 1.1.1
npm ERR! path /home/admin/node_modules/socket.io/node_modules/socket.io-client/node_modules/___xmlhttprequest.npm/package/package.json
npm ERR! fstream_path /home/admin/node_modules/socket.io/node_modules/socket.io-client/node_modules/___xmlhttprequest.npm/package/package.json
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! message ENOENT, no such file or directory '/home/admin/node_modules/socket.io/node_modules/socket.io-client/node_modules/___xmlhttprequest.npm/package/package.json'
npm ERR! errno {}
npm ERR! fstream_stack Object.oncomplete (/home/admin/local/lib/node_modules/npm/node_modules/fstream/lib/writer.js:204:26)
npm ERR! error rolling back socket.io-client#0.8.7 Error: UNKNOWN, unknown error '/home/admin/node_modules/socket.io/node_modules/socket.io-client/node_modules/___uglify-js.npm/package'
npm ERR! error installing socket.io#0.8.7
npm ERR! Error: ENOENT, no such file or directory '/home/admin/node_modules/socket.io/node_modules/socket.io-client/node_modules/websocket-client/package.json'
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!
npm ERR! System Linux 2.6.32.2-xxxx-grs-ipv6-32
npm ERR! command "node" "/home/admin/local/bin/npm" "install" "socket.io"
npm ERR! cwd /home/admin
npm ERR! node -v v0.6.10
npm ERR! npm -v 1.1.1
npm ERR! path /home/admin/node_modules/socket.io/node_modules/socket.io-client/node_modules/websocket-client/package.json
npm ERR! code ENOENT
npm ERR! message ENOENT, no such file or directory '/home/admin/node_modules/socket.io/node_modules/socket.io-client/node_modules/websocket-client/package.json'
npm ERR! errno {}
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/admin/npm-debug.log
npm not ok
I tried to install the forever module for node.js on my windows server, but got this error:
C:\rts_lobby>npm install forever
npm http GET https://registry.npmjs.org/forever
npm http 200 https://registry.npmjs.org/forever
npm http GET https://registry.npmjs.org/forever/-/forever-0.8.5.tgz
npm http 200 https://registry.npmjs.org/forever/-/forever-0.8.5.tgz
(...snip...)
npm http GET https://registry.npmjs.org/parse-table
> microtime#0.2.0 install C:\rts_lobby\node_modules\forever\node_modules\microti
me
> node-waf configure build
npm http GET https://registry.npmjs.org/mkdirp
npm http GET https://registry.npmjs.org/lazy
npm http GET https://registry.npmjs.org/eventemitter2
'node-waf' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! error installing microtime#0.2.0
npm http GET https://registry.npmjs.org/prompt/0.1.12
(...snip...)
npm http GET https://registry.npmjs.org/mkdirp
> node-fork#0.4.1 preinstall C:\rts_lobby\node_modules\forever\node_modules\node
-fork
> bash ./install
npm http 200 https://registry.npmjs.org/parse-table
npm http 304 https://registry.npmjs.org/mkdirp
> daemon#0.4.1 preinstall C:\rts_lobby\node_modules\forever\node_modules\daemon
> bash ./install
npm http 200 https://registry.npmjs.org/lazy
npm http GET https://registry.npmjs.org/wordwrap
'bash' is not recognized as an internal or external command,
operable program or batch file.
'bash' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! error installing daemon#0.4.1
npm ERR! error installing node-fork#0.4.1
npm ERR! error installing forever#0.8.5
npm http 200 https://registry.npmjs.org/eventemitter2
npm http 200 https://registry.npmjs.org/lru-cache
npm http GET https://registry.npmjs.org/mkdirp/-/mkdirp-0.0.7.tgz
npm ERR! EEXIST, file already exists 'C:\rts_lobby\node_modules\forever\node_mod
ules\___nconf.npm\package\lib\nconf'
npm ERR! File exists: C:\rts_lobby\node_modules\forever\node_modules\___nconf.np
m\package\lib\nconf
npm ERR! Move it away, and try again.
npm ERR!
npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\\Program Files (x86)\\nodejs\\\\node.exe" "C:\\Program File
s (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "forever"
npm ERR! cwd C:\rts_lobby
npm ERR! node -v v0.6.8
npm ERR! npm -v 1.1.0-2
npm ERR! path C:\rts_lobby\node_modules\forever\node_modules\___nconf.npm\packag
e\lib\nconf
npm ERR! fstream_path C:\rts_lobby\node_modules\forever\node_modules\___nconf.np
m\package\lib\nconf\common.js
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code EEXIST
npm ERR! message EEXIST, file already exists 'C:\rts_lobby\node_modules\forever\
node_modules\___nconf.npm\package\lib\nconf'
npm ERR! errno {}
npm ERR! fstream_stack C:\Program Files (x86)\nodejs\node_modules\npm\node_modul
es\fstream\lib\writer.js:161:23
npm ERR! fstream_stack Object.oncomplete (C:\Program Files (x86)\nodejs\node_mod
ules\npm\node_modules\mkdirp\index.js:25:53)
npm ERR! Error: ENOENT, no such file or directory 'C:\rts_lobby\node_modules\for
ever\node_modules\___broadway.npm\package\test\common\directories-test.js'
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!
npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\\Program Files (x86)\\nodejs\\\\node.exe" "C:\\Program File
s (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "forever"
npm ERR! cwd C:\rts_lobby
npm ERR! node -v v0.6.8
npm ERR! npm -v 1.1.0-2
npm ERR! path C:\rts_lobby\node_modules\forever\node_modules\___broadway.npm\pac
kage\test\common\directories-test.js
npm ERR! fstream_path C:\rts_lobby\node_modules\forever\node_modules\___broadway
.npm\package\test\common\directories-test.js
npm ERR! fstream_type File
npm ERR! fstream_class FileWriter
npm ERR! code ENOENT
npm ERR! message ENOENT, no such file or directory 'C:\rts_lobby\node_modules\fo
rever\node_modules\___broadway.npm\package\test\common\directories-test.js'
npm ERR! errno {}
npm ERR! fstream_stack Object.oncomplete (C:\Program Files (x86)\nodejs\node_mod
ules\npm\node_modules\fstream\lib\writer.js:204:26)
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! C:\rts_lobby\npm-debug.log
npm not ok
I wouldn't think I was doing anything wrong, but who knows? Anyone have any idea why this may not be working? I'm guessing it has to do with node-waf, which isn't on my system for some reason. Is this not included by default?
I had the same issue installing forever 0.8.4+ on Windows. It seems node-waf is not even available for Windows. Installed forever 0.8.3 as a workaround - just run:
npm install forever=0.8.3
On windows, the best way to keep node running is to use iisnode - http://tomasz.janczuk.org/2011/08/hosting-nodejs-applications-in-iis-on.html and http://weblogs.asp.net/jgalloway/archive/2011/10/26/using-node-js-in-an-asp-net-mvc-application-with-iisnode.aspx
Agree that it is not ideal in all situations, but that is the best we have currently.
I assume you using Cygwin? It looks like you either A) did not install bash via cygwin packages or it isn't in your PATH
If you are not using cygwin, you may want to use it because it looks like this package has system dependencies for some linux commands in it's install scripts.