search

rickyrauch / Balloons.IO

Balloons.IO is a web multi-room chat server and client ready to use. It’s built with the help of node.JS, Express, Socket.IO and Redis. Balloons uses PassportJS for authentication with Twitter and Facebook
http://balloons.io
2.36k stars 491 forks source link

Problem during Installation [ 'component-type' is not in the npm registry ] #90

Closed nik0202 closed 11 years ago

nik0202 commented 11 years ago

I am facing problem during installation of Balloons.IO

After cloning Balloons.IO when I do "npm install" it gives following error.

npm ERR! 404 'component-type' is not in the npm registry. npm ERR! 404 You should bug the author to publish it

nav16 commented 11 years ago

I am facing the same issue.

How can it be resolved.

cristiandouce commented 11 years ago

@imnpandey @nik0202 Please check in case I'm wrong, but I think github urls like component/type are supported from npm@1.1.64. And there was a fix at npm@1.2.20. Would you mind check which version you have? I'll update the engines path at package.json as soon as you can confirm that this solves the issue.

Thanks!

nav16 commented 11 years ago

Issue was solved by cloning the source using git. But when the code is downloaded in zip/tar the error persists.

node -v v0.10.15 npm -v 1.3.5

cristiandouce commented 11 years ago

@imnpandey Ok, that's odd! :facepunch:

I will try it myself. Thanks for the information!

marg51 commented 11 years ago

I am facing the same issue.

git clone https://github.com/gravityonmars/Balloons.IO.git
npm install

npm http 304 https://registry.npmjs.org/cookie npm http 404 https://registry.npmjs.org/component-type npm http 304 https://registry.npmjs.org/debug [...] 404 'component-type' is not in the npm registry node -v v0.10.9 npm -v 1.2.24

Hope this helps

rickyrauch commented 11 years ago

Can you try again, maybe npmjs.org wasn't working.

marg51 commented 11 years ago

same error.

I fixed it by replacing "component-type": "component/type" -> "type-component": "0.0.1" into package.json type = require('component-type'); -> type = require('type-component'); into utils.js

I don't know if the module has been renamed or if it is another, but everything seems to work

cristiandouce commented 11 years ago

We are not fetching that module from npmjs.org but from github instead. That's the reason of the odd sintax. It's how npm fetches from github. Since the npmjs.org version of component-type is not up to date, we were force to fetch it from github.

I'm having no troubles with node@0.10.2 and npm@1.2.15

So far, this error seems to appear randomly.