os: windows 7 64bit
behind company proxy, set proxy like this:
npm config set proxy http://username:abcd1\!@proxy.company.com:81
npm config set https-proxy http://username:abcd11\!@proxy.company.com:81
can successfully install firstname.lastname@example.org:
npm install email@example.com
but failed to install the latest version 1.0.6:
npm install socket.io
part of the error log:
880 silly lockFile 9cb95944--npmjs-org-json3-json3-3-2-6-tgz http://registry.npmjs.org/json3/-/json3-3.2.6.tgz
881 verbose lock http://registry.npmjs.org/json3/-/json3-3.2.6.tgz C:\Users\dengzhl9\AppData\Roaming\npm-cache\9cb95944--npmjs-org-json3-json3-3-2-6-tgz.lock
882 verbose addRemoteTarball [ 'http://registry.npmjs.org/json3/-/json3-3.2.6.tgz',
882 verbose addRemoteTarball 'f6efc93c06a04de9aec53053df2559bb19e2038b' ]
883 info retry fetch attempt 1 at 12:16:52
884 verbose fetch to= c:\temp\npm-35944-RT6xEBbm\1405570612244-0.050692107528448105\tmp.tgz
885 http GET http://registry.npmjs.org/json3/-/json3-3.2.6.tgz
886 error TypeError: Request path contains unescaped characters.
886 error at new ClientRequest (_http_client.js:73:11)
886 error at TunnelingAgent.exports.request (http.js:52:10)
886 error at TunnelingAgent.createSocket (d:\software\install\nodejs\node_modules\npm\node_modules\request\node_modules\tunnel-agent\index.js:117:25)
886 error at TunnelingAgent.createSecureSocket [as createSocket] (d:\software\install\nodejs\node_modules\npm\node_modules\request\node_modules\tunnel-agent\index.js:184:41)
886 error at TunnelingAgent.addRequest (d:\software\install\nodejs\node_modules\npm\node_modules\request\node_modules\tunnel-agent\index.js:80:8)
886 error at new ClientRequest (_http_client.js:153:16)
886 error at Object.exports.request (http.js:52:10)
886 error at Object.exports.request (https.js:136:15)
886 error at Request.start (d:\software\install\nodejs\node_modules\npm\node_modules\request\request.js:583:30)
886 error at Request.end (d:\software\install\nodejs\node_modules\npm\node_modules\request\request.js:1237:28)
887 error If you need help, you may report this *entire* log,
887 error including the npm and node versions, at:
887 error <http://github.com/npm/npm/issues>
888 error System Windows_NT 6.1.7601
889 error command "d:\\software\\install\\nodejs\\node.exe" "d:\\software\\install\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "socket.io"
890 error cwd d:\temp\koa
891 error node -v v0.11.13
892 error npm -v 1.4.9
893 verbose exit [ 1, true ]
I have this same issue, too. I notice that it happens whenever a tar.gz file is what is to be downloaded. I tried downloading it with curl (in the git bash on Win7) and it sits downloading, but never progresses and stays at 0 bytes downloaded. For some of the packages, I can just run npm install json3, and it downloads just fine. However, some packages, such as emitter will not download and install by running npm install emitter.
Here's a log from trying to download with curl.
npm version: 1.3.22
node version: v0.11.10
$ curl http://github.com/component/emitter/archive/1.0.1.tar.gz -o node_modules/emitter -v
* Adding handle: conn: 0x220d830
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0x220d830) send_pipe: 1, recv_pipe: 0
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0*
About to connect() to github.com port 80 (#0)
* Trying 220.127.116.11...
0 0 0 0 0 0 0 0 --:--:-- 0:00:20 --:--:-- 0*
* Failed connect to github.com:80; No error
* Closing connection 0
curl: (7) Failed connect to github.com:80; No error
@bjackson, part of your issue is that you are using a very old version of npm and / or Node. The current version of npm is 2.1.3, and you can get firstname.lastname@example.org out of the box by upgrading to the most recent version of Node using the official Windows installer. Also, your problem with curl is not at all connected to npm, because npm is involved nowhere in the connection between curl and GitHub's file servers. Good luck figuring out what's happening!
@superbull, are you still having this problem with newer versions of npm? Sorry for not responding sooner (our support backlog is very, very deep), but I believe that the versions of request we've upgraded to along the way to email@example.com include a number of patches to the tunneling agent that might have addressed your issue.
Thanks. I upgraded and, sure enough, I was able to install.
Can this issue be closed?
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!)
Closing as resolved / abandoned.