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

NMP install broken #335

Closed
tanepiper opened this issue Feb 7, 2013 · 14 comments
Closed

NMP install broken #335

tanepiper opened this issue Feb 7, 2013 · 14 comments

Comments

@tanepiper
Copy link

Latest version of Testacular install is broken - it looks like Socket.io-client is breaking it:

╰─○ sudo npm install -g testacular
npm http GET https://registry.npmjs.org/testacular
npm http 304 https://registry.npmjs.org/testacular
npm http GET https://registry.npmjs.org/socket.io
npm http GET https://registry.npmjs.org/chokidar
npm http GET https://registry.npmjs.org/glob
npm http GET https://registry.npmjs.org/optimist
npm http GET https://registry.npmjs.org/coffee-script
npm http GET https://registry.npmjs.org/minimatch
npm http GET https://registry.npmjs.org/xmlbuilder
npm http GET https://registry.npmjs.org/http-proxy
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/coffee-script
npm http 304 https://registry.npmjs.org/glob
npm http 304 https://registry.npmjs.org/minimatch
npm http 304 https://registry.npmjs.org/xmlbuilder
npm http 304 https://registry.npmjs.org/http-proxy
npm http GET https://registry.npmjs.org/lru-cache
npm http GET https://registry.npmjs.org/sigmund
npm http GET https://registry.npmjs.org/graceful-fs
npm http GET https://registry.npmjs.org/inherits
npm http GET https://registry.npmjs.org/wordwrap
npm http GET https://registry.npmjs.org/policyfile/0.0.4
npm http GET https://registry.npmjs.org/base64id/0.1.0
npm http GET https://registry.npmjs.org/socket.io-client/0.9.11
npm http GET https://registry.npmjs.org/redis/0.7.3
npm http GET https://registry.npmjs.org/colors
npm http GET https://registry.npmjs.org/pkginfo
npm http 304 https://registry.npmjs.org/sigmund
npm http 304 https://registry.npmjs.org/graceful-fs
npm http 304 https://registry.npmjs.org/wordwrap
npm http 304 https://registry.npmjs.org/lru-cache
npm http 304 https://registry.npmjs.org/inherits
npm http 304 https://registry.npmjs.org/policyfile/0.0.4
npm http 304 https://registry.npmjs.org/base64id/0.1.0
npm http 304 https://registry.npmjs.org/redis/0.7.3
npm http 304 https://registry.npmjs.org/socket.io-client/0.9.11
npm http 304 https://registry.npmjs.org/colors
npm http 304 https://registry.npmjs.org/pkginfo
npm http GET https://registry.npmjs.org/uglify-js/1.2.5
npm http GET https://registry.npmjs.org/ws
npm http GET https://registry.npmjs.org/xmlhttprequest/1.4.2
npm http GET https://registry.npmjs.org/active-x-obfuscator/0.0.1
npm http 304 https://registry.npmjs.org/xmlhttprequest/1.4.2
npm http 304 https://registry.npmjs.org/active-x-obfuscator/0.0.1
npm http 304 https://registry.npmjs.org/uglify-js/1.2.5
npm http 304 https://registry.npmjs.org/ws
npm http GET https://registry.npmjs.org/zeparser/0.0.5
npm http GET https://registry.npmjs.org/commander
npm http GET https://registry.npmjs.org/tinycolor
npm http GET https://registry.npmjs.org/options
npm http 304 https://registry.npmjs.org/zeparser/0.0.5
npm http 304 https://registry.npmjs.org/tinycolor
npm http 304 https://registry.npmjs.org/options
npm http 304 https://registry.npmjs.org/commander

> [email protected] install /usr/local/lib/node_modules/testacular/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)


npm ERR! TypeError: options.uid should be a number
npm ERR!     at ChildProcess.spawn (child_process.js:782:24)
npm ERR!     at Object.exports.spawn (child_process.js:618:9)
npm ERR!     at spawn (/usr/lib/node_modules/npm/lib/utils/exec.js:103:22)
npm ERR!     at exec (/usr/lib/node_modules/npm/lib/utils/exec.js:40:12)
npm ERR!     at /usr/lib/node_modules/npm/lib/utils/lifecycle.js:146:5
npm ERR!     at process.startup.processNextTick.process._tickCallback (node.js:244:9)
npm ERR! You may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <[email protected]>
npm ERR! 
npm ERR! System Darwin 12.2.0
npm ERR! command "node" "/usr/bin/npm" "install" "-g" "testacular"
npm ERR! cwd /Users/freeagent/build/node-v0.8.19
npm ERR! node -v v0.8.19
npm ERR! npm -v 1.1.16
npm ERR! message options.uid should be a number
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/freeagent/build/node-v0.8.19/npm-debug.log
npm not ok
@bitwiseman
Copy link
Contributor

What about sudo npm install -g testacular@canary?

@bitwiseman
Copy link
Contributor

From the log it looks like npm believes it has a bug. You might report it to npm group as well.

@vojtajina
Copy link
Contributor

Can you try to remove npm cache (rm -rf ~/.npm) and install it again ?

@vojtajina
Copy link
Contributor

Closing. Please re-open if you think it's a testacular issue.

@rbudiharso
Copy link

I have this error when trying to install karma on OS X

GuiE

@dignifiedquire
Copy link
Member

@rahmat-budiharso What version of node are you running? Try updating to 10.2.

@vojtajina
Copy link
Contributor

Yep, there was a bug in NPM that has been fixed in 0.10.2

@rbudiharso
Copy link

I have npm 1.2.15, but I manage to solve this by installing ws module version 0.4.24

$ npm install -g [email protected]
$ npm install -g karma

@vizion123mix
Copy link

While trying to install karma today ran into this issue
Screen Shot 2013-04-12 at 5 14 37 PM

Just installed node.js flawlessly. I have tried all the steps mentioned above from clearing npm cache to running to install command via the sudo command. Nothing works...

@vojtajina
Copy link
Contributor

@rahmat-budiharso @vizion123mix what is the error ? The outputs you sent didn't contain any error... at least I don't see it...

@rbudiharso
Copy link

The error happens before I installed ws version 0.4.24, it looks like ws 0.4.25 has some problem. When I try to install karma, it installing ws 0.4.25 as dependency, but that failed, so I manually install ws 0.4.24 which is fine and then continued with installing karma again which runs fine with ws already installed. So I presume ws 0.4.25 has its own problem :)

@vojtajina
Copy link
Contributor

I think that might be related to websockets/ws#178

@vizion123mix
Copy link

I think it might be, however after reading rahmat's comment,

  1. i went and installed all the dependencies for ws manually
  2. installed ws manually
  3. install karma using "$ npm install karma" command.
  4. karma installed fine after that.

In regards to vojtajina comment. I think ws is included as a dependency in the new karma build. I had no issues with my node installation.

@vojtajina
Copy link
Contributor

ws is a dependency of socket.io, it's dependency as any other (but it
contains building process, as it's a native module)

On Thu, Apr 18, 2013 at 6:01 PM, Rene Robles [email protected]:

I think it might be, however after reading rahmat's comment,

  1. i went and installed all the dependencies for ws manually
  2. installed ws manually
  3. install karma using "$ npm install karma" command.
  4. karma installed fine after that.

In regards to vojtajina comment. I think ws is included as a dependency in
the new karma build. I had no issues with my node installation.


Reply to this email directly or view it on GitHubhttps://github.com//issues/335#issuecomment-16622288
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants