npm install fails due to dependency not found #84
Comments
|
This dependency is linked to a github fork because of a pending problem with the npm release of I just tried from a clean npm cache and it works as expected; I see install in the npm stats too. Looks like your git client could not connect to github. This could be a temporary glitch or maybe have something to do with your local network situation (proxies etc). Can you check if you can do regular git clones from github? Do you have a somewhat recent version of the git command-line client? On windows I use the one that comes with TortoiseGIT. |
|
Tried it now, everything seems to work. Maybe temp glitch 👍 |
|
Cool, it can happen occasionally. I'll close the issue then. |
|
ninja response 💯 |
|
Looks like this is the same thing the OP had: for some reason your local git client could not get the dependency from github. For him it resolved itself on after a few retries (I guess it was some network thing). You can see it in this bit: If it still doesn't work you could see if your npm version and your git client are recent. I'm aware this is annoying (this is at least the third time this is reported), so for the next TSD release I'll try to get rid of this git dependency (if I get my fixes for the |
|
thanks a lot, i will try |
|
Hi I started this thread. What resolved it is taking the laptop home and pulling from my home network. I guess there is something in corporate network administration that blocks ports that git client uses. Try it at a different network or find out which ports are blocked. |
|
@kostaad For my info: do you use git at work for other tasks? (eg: do we know if the problem is with git itself or more in the the way npm uses it?) |
|
@Bartvds We do not use git extensively at work, maybe to pull some projects off github occasionally and it seems to work, the only time I noticed this problem is with this dependency update-notifier on this project through NPM. Every other way of using git (and not extensively again) worked. |
|
@kostaad Thanks for the info: I'm googling for this and I think that makes sense: The problem seems to be the The reason you might not have seen this before could be that github usually shows a |
|
@chaosmail I pushed a change to the package.json that might fix this by using git over https: Could you try to install from the repos using this command? |
|
@Bartvds thanks, that helped! |
|
Awesome, thanks for the confirmation. I've wondered why this protocol choice was possible but couldn't figure, now we know. A downside of this update-notifier thing is that all users will get an update-note if I push this fix to npm so I'll have to see when to publish this. Probably part of next big update, so I'll close this again (for now 😉) |
applied git:// url fix of #84 updated chai to 1.9.x - updated typing - fixed deprecation
|
For the archive, another workaround (via reddit): This works when using TSD as dependency, like from grunt-tsd: Config git to transform git urls to https. Of course this is less useful if you need to use legitimate git urls with hosts that don't support https. |
|
|
|
@spidgorny Would that be good magic or bad magic? |
|
Thanks @Bartvds ! The fix that worked for me is: |
|
Thanks @Bartvds !! |
|
Thx @Bartvds it works ! |
|
Actually I was stuck with the same problem . Here's how I fixed it .
|
Hi tried, to install with npm install and got this:
npm ERR! git fetch -a origin (git://github.com/Bartvds/update-notifier/) fatal: unable to connect to github.com:
npm ERR! git fetch -a origin (git://github.com/Bartvds/update-notifier/) github.com[0: 192.30.252.129]: errno=No such file or directory
npm ERR! Error: Command failed: fatal: unable to connect to github.com:
npm ERR! github.com[0: 192.30.252.129]: errno=No such file or directory
npm ERR!
npm ERR!
npm ERR! at ChildProcess.exithandler (child_process.js:637:15)
npm ERR! at ChildProcess.EventEmitter.emit (events.js:98:17)
npm ERR! at maybeClose (child_process.js:743:16)
npm ERR! at Process.ChildProcess._handle.onexit (child_process.js:810:5)
npm ERR! If you need help, you may report this entire log,
npm ERR! including the npm and node versions, at:
npm ERR! https://github.com/npm/npm/issues
npm ERR! System Windows_NT 6.2.9200
npm ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "grunt-tsd" "-g"
npm ERR! cwd C:\dev\iandmine\Source\Client
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.3
npm ERR! code 128
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! C:\dev\iandmine\Source\Client\npm-debug.log
npm ERR! not ok code 0
The text was updated successfully, but these errors were encountered: