Skip to content

cannot install karma #4543

Closed
Rajavelu opened this Issue Jan 24, 2014 · 6 comments

6 participants

@Rajavelu
rajavelu-1469@rajavelu-1469:~/pt2/pt2-server/webapps/predict$ npm install karma
npm WARN package.json pt@0.0.1 No description
npm WARN package.json pt@0.0.1 No repository field.
npm WARN package.json pt@0.0.1 No README data
npm WARN package.json express-namespace@0.1.1 No repository field.
npm http GET https://registry.npmjs.org/karma
npm http GET https://registry.npmjs.org/karma
npm http GET https://registry.npmjs.org/karma
npm http GET https://registry.npmjs.org/karma/-/karma-0.10.8.tgz
npm ERR! fetch failed https://registry.npmjs.org/karma/-/karma-0.10.8.tgz
npm http GET https://registry.npmjs.org/karma/-/karma-0.10.8.tgz
npm ERR! fetch failed https://registry.npmjs.org/karma/-/karma-0.10.8.tgz
npm http GET https://registry.npmjs.org/karma/-/karma-0.10.8.tgz
npm ERR! fetch failed https://registry.npmjs.org/karma/-/karma-0.10.8.tgz
npm ERR! network tunneling socket could not be established, cause=139883168200512:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:../deps/openssl/openssl/ssl/s23_clnt.c:766:
npm ERR! network 
npm ERR! network This is most likely not a problem with npm itself
npm ERR! network and is related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network 
npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly.  See: 'npm help config'

npm ERR! System Linux 3.2.0-54-generic
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "install" "karma"
npm ERR! cwd /home/likewise-open/ZOHOCORP/rajavelu-1469/pt2/pt2-server/webapps/predict
npm ERR! node -v v0.10.23
npm ERR! npm -v 1.3.17
npm ERR! code ECONNRESET
npm ERR! 
@Swaagie
Swaagie commented Jan 24, 2014

Not a npm issue, most likely related to the outage, see http://blog.nodejitsu.com/npm-post-mortem-01-24/

@gobblygeek

Actually, I'm still getting something similar, and my impression was that the outage was over:

C:\Users\jennifer_ayers\Desktop\workspace\localtests\angular-seed-master>npm ins
tall - g karma@0.8.7
npm http GET https://registry.npmjs.org/karma/0.8.7
npm http GET https://registry.npmjs.org/%E2%80%93
npm http GET https://registry.npmjs.org/g
npm http 403 https://registry.npmjs.org/%E2%80%93
npm ERR! TypeError: Cannot read property 'latest' of undefined
npm ERR! at next (C:\Program Files\nodejs\node_modules\npm\lib\cache.js:688:
35)
npm ERR! at C:\Program Files\nodejs\node_modules\npm\lib\cache.js:676:5
npm ERR! at saved (C:\Program Files\nodejs\node_modules\npm\node_modules\npm
-registry-client\lib\get.js:142:7)
npm ERR! at C:\Program Files\nodejs\node_modules\npm\node_modules\graceful-f
s\polyfills.js:133:7
npm ERR! at Object.oncomplete (fs.js:107:15)
npm ERR! If you need help, you may report this entire log,
npm ERR! including the npm and node versions, at:
npm ERR! http://github.com/isaacs/npm/issues

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\Program Files\nodejs\\node.exe" "C:\Program Files\nod
ejs\node_modules\npm\bin\npm-cli.js" "install" "-" "g" "karma@0.8.7"
npm ERR! cwd C:\Users\jennifer_ayers\Desktop\workspace\localtests\angular-seed-m
aster
npm ERR! node -v v0.10.24
npm ERR! npm -v 1.3.21
npm ERR! type non_object_property_load
npm http 403 https://registry.npmjs.org/g
npm ERR! TypeError: Cannot read property 'latest' of undefined
npm ERR! at next (C:\Program Files\nodejs\node_modules\npm\lib\cache.js:688:
35)
npm ERR! at C:\Program Files\nodejs\node_modules\npm\lib\cache.js:676:5
npm ERR! at saved (C:\Program Files\nodejs\node_modules\npm\node_modules\npm
-registry-client\lib\get.js:142:7)
npm ERR! at C:\Program Files\nodejs\node_modules\npm\node_modules\graceful-f
s\polyfills.js:133:7
npm ERR! at Object.oncomplete (fs.js:107:15)
npm ERR! If you need help, you may report this entire log,
npm ERR! including the npm and node versions, at:
npm ERR! http://github.com/isaacs/npm/issues

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\Program Files\nodejs\\node.exe" "C:\Program Files\nod
ejs\node_modules\npm\bin\npm-cli.js" "install" "-" "g" "karma@0.8.7"
npm ERR! cwd C:\Users\jennifer_ayers\Desktop\workspace\localtests\angular-seed-m
aster
npm ERR! node -v v0.10.24
npm ERR! npm -v 1.3.21
npm ERR! type non_object_property_load
npm http 503 https://registry.npmjs.org/karma/0.8.7
npm ERR! registry error parsing json
npm http GET https://registry.npmjs.org/karma/0.8.7
npm http 503 https://registry.npmjs.org/karma/0.8.7
npm ERR! registry error parsing json
npm http GET https://registry.npmjs.org/karma/0.8.7
npm http 404 https://registry.npmjs.org/karma/0.8.7
npm ERR! Error: No dist in undefined package
npm ERR! at next (C:\Program Files\nodejs\node_modules\npm\lib\cache.js:749:
26)
npm ERR! at C:\Program Files\nodejs\node_modules\npm\lib\cache.js:742:5
npm ERR! at saved (C:\Program Files\nodejs\node_modules\npm\node_modules\npm
-registry-client\lib\get.js:142:7)
npm ERR! at C:\Program Files\nodejs\node_modules\npm\node_modules\graceful-f
s\polyfills.js:133:7
npm ERR! at Object.oncomplete (fs.js:107:15)
npm ERR! If you need help, you may report this entire log,
npm ERR! including the npm and node versions, at:
npm ERR! http://github.com/isaacs/npm/issues

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\Program Files\nodejs\\node.exe" "C:\Program Files\nod
ejs\node_modules\npm\bin\npm-cli.js" "install" "-" "g" "karma@0.8.7"
npm ERR! cwd C:\Users\jennifer_ayers\Desktop\workspace\localtests\angular-seed-m
aster
npm ERR! node -v v0.10.24
npm ERR! npm -v 1.3.21
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! C:\Users\jennifer_ayers\Desktop\workspace\localtests\angular-seed-m
aster\npm-debug.log
npm ERR! not ok code 0

@Swaagie
Swaagie commented Jan 29, 2014

Outage is def over, but this error is also different from above issue

@gobblygeek

Any recommendations on how to fix it?

@iarna iarna added the support label Oct 3, 2014
@smikes
smikes commented Feb 2, 2015

Is this still a problem for you?

It looks like - and g were being interpreted as two distinct options instead of as a flag (-g), leading to an error when the packages named - g were not found in the registry.

There have been a lot of improvements to npm -- especially around conflicts and race conditions during install -- since January 2014. Can you try updating your npm installation?

To update npm on Windows, follow the instructions here: https://github.com/npm/npm/wiki/Troubleshooting#upgrading-on-windows

We are trying to clean up older npm issues, so if we don't hear back from you within a week, we will close this issue. (Don't worry -- you can always come back again and open a new issue!)

Thanks!

@othiym23

Closing as resolved long, long ago.

@othiym23 othiym23 closed this Apr 29, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.