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

npm install error since 0.14.3 #221

Closed
glendacaine opened this issue May 20, 2013 · 12 comments
Closed

npm install error since 0.14.3 #221

glendacaine opened this issue May 20, 2013 · 12 comments

Comments

@glendacaine
Copy link

Hi

I have just tried installing superagent, but since the upgrade to 0.14.3 I am getting the following errors (0.14.2 is still fine)

npm WARN git config --get remote.origin.url returned wrong result (git://github.com/RedVentures/reduce) undefined
npm WARN git config --get remote.origin.url returned wrong result (git://github.com/RedVentures/reduce) undefined
npm WARN package.json methods@0.0.1 No README.md file found!
npm ERR! git clone git://github.com/RedVentures/reduce undefined
npm ERR! git clone git://github.com/RedVentures/reduce undefined
npm WARN git config --get remote.origin.url returned wrong result (git://github.com/component/emitter) undefined
npm WARN git config --get remote.origin.url returned wrong result (git://github.com/component/emitter) undefined
npm ERR! git clone git://github.com/component/emitter undefined
npm ERR! git clone git://github.com/component/emitter undefined
npm ERR! Error: No compatible version found: reduce@'RedVentures/reduce#346d59'
npm ERR! Valid install targets:
npm ERR! ["0.1.0"]
npm ERR! at installTargetsError (/usr/local/lib/node_modules/npm/lib/cache.js:685:10)
npm ERR! at /usr/local/lib/node_modules/npm/lib/cache.js:607:10
npm ERR! at saved (/usr/local/lib/node_modules/npm/node_modules/npm-registry-client/lib/get.js:138:7)
npm ERR! at Object.oncomplete (fs.js:107:15)
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.5.0-23-generic
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install" "superagent"
npm ERR! cwd /home/glenda/sensemaking/projects/shindigger/api
npm ERR! node -v v0.10.5
npm ERR! npm -v 1.2.18
npm http 304 https://registry.npmjs.org/qs/0.5.6
npm http 304 https://registry.npmjs.org/formidable/1.0.9
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home/glenda/sensemaking/projects/shindigger/api/npm-debug.log
npm ERR! not ok code 0

@pwldp
Copy link

pwldp commented May 20, 2013

According to the https://gemnasium.com/visionmedia/superagent "emitter" latest version is 0.0.2.
In package.json is 1.0.0.
It should be "emitter" or "component/emitter"?

@georgesnelling
Copy link

We see a blocking install problem with 0.14.3 on windows only. Osx is fine. on windows, npm cannot find emitter and chokes.

@tj
Copy link
Contributor

tj commented May 20, 2013

did you guys update npm for GH style support?

@tj
Copy link
Contributor

tj commented May 20, 2013

it's "emitter-component" in npm, I forget why someone needed to change it to GH-style, but it's the same project

@georgesnelling
Copy link

we're running

node 0.10.4
npm 1.2.18

on both windows and osx. npm install superagent works on osx, chokes on windows complaining it can't find both the dependencies mentioned in the top-line report. haven't had time to grovel the npm commit logs. If its a general npm / windows problem I'm sure the Dear Leader will hear about it soon.

@pwldp
Copy link

pwldp commented May 21, 2013

My problem exists on LInux.
What does it mean: npm in GH-style? It is different npm manager?

@jdesboeufs
Copy link

It happens when git is not available.

@tj
Copy link
Contributor

tj commented May 21, 2013

wonder why npm doesn't grab the tarball instead

@ericelliott
Copy link

@visionmedia I'm seeing this issue as well. It can't find a compatible version of component/emitter.

I worked around it by locking superagent at 0.14.2. It's saying it can't find a compatible version.

Interestingly, this works just fine:

$ npm install emitter-component
npm http GET https://registry.npmjs.org/emitter-component
npm http 200 https://registry.npmjs.org/emitter-component
npm http GET https://registry.npmjs.org/emitter-component/-/emitter-component-1.0.0.tgz
npm http 200 https://registry.npmjs.org/emitter-component/-/emitter-component-1.0.0.tgz
emitter-component@1.0.0 node_modules/emitter-component

@tj
Copy link
Contributor

tj commented May 22, 2013

that dep is only for the client version anyway, this is kind of why npm sucks for both server and client side code, that dep is completely useless for the server end. im going to revert that commit, browserify people will just have to suffer

@tj
Copy link
Contributor

tj commented May 22, 2013

0.14.4

@tj tj closed this as completed May 22, 2013
@ericelliott
Copy link

Working like a charm for me in Node again. Thanks.

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