> npm ERR! System Windows_NT 5.1.2600
> npm ERR! command "C:\\Programme\\nodejs\\\\node.exe"
> "C:\\Programme\\nodejs\\nod
> e_modules\\npm\\bin\\npm-cli.js" "search" "yuidoc"
> npm ERR! cwd H:\
> npm ERR! node -v v0.8.3
> npm ERR! npm -v 1.1.43
> npm ERR! code ECONNRESET
> npm ERR!
> npm ERR! Additional logging details can be found in:
> npm ERR!     H:\npm-debug.log
> npm ERR! not ok code 0

> H:\>

> I got some trouble using node and the install from npm.

> I want to make some documentation with YUI.
> In order so to do I tried to install it with npm, but it gives me
> Errormessages like the following, for everything I do with npm, like npm
> search

>> H:\>npm search yuidoc
>> npm WARN Building the local index for the first time, please be patient
>> npm http GET https://registry.npmjs.org/-/all
>> npm http GET https://registry.npmjs.org/-/all
>> npm http GET https://registry.npmjs.org/-/all
>> npm ERR! Error: tunneling socket could not be established, cause=Parse
>> Error
>> npm ERR!     at ClientRequest.onError
>> (C:\Programme\nodejs\node_modules\npm\node_modules\request\tunnel.js:161:17 )
>> npm ERR!     at ClientRequest.g (events.js:185:14)
>> npm ERR!     at ClientRequest.EventEmitter.emit (events.js:88:17)
>> npm ERR!     at Socket.socketErrorListener (http.js:1320:9)
>> npm ERR!     at Socket.EventEmitter.emit (events.js:88:17)
>> npm ERR!     at Socket._destroy.self.errorEmitted (net.js:329:14)
>> npm ERR!     at process.startup.processNextTick.process._tickCallback
>> (node.js:244:9)
>> 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 Windows_NT 5.1.2600
>> npm ERR! command "C:\\Programme\\nodejs\\\\node.exe"
>> "C:\\Programme\\nodejs\\nod
>> e_modules\\npm\\bin\\npm-cli.js" "search" "yuidoc"
>> npm ERR! cwd H:\
>> npm ERR! node -v v0.8.3
>> npm ERR! npm -v 1.1.43
>> npm ERR! code ECONNRESET
>> npm ERR!
>> npm ERR! Additional logging details can be found in:
>> npm ERR!     H:\npm-debug.log
>> npm ERR! not ok code 0

>> H:\>

> I'm behind a corporate Proxy. I don't know if that helps. I already tried
> npm config set proxy http://...

> Plus when i try npm config list all i get is this (from npm-debug.log)

>> 0 info it worked if it ends with ok
>> 1 verbose cli [ 'C:\\Programme\\nodejs\\\\node.exe',
>> 1 verbose cli
>> 'C:\\Programme\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
>> 1 verbose cli   'config',
>> 1 verbose cli   'list' ]
>> 2 info using n...@1.1.43
>> 3 info using n...@v0.8.3
>> 4 verbose node symlink C:\Programme\nodejs\\node.exe
>> 5 verbose config file C:\Dokumente und Einstellungen\user\.npmrc
>> 6 verbose config file C:\Programme\nodejs\etc\npmrc
>> 7 verbose config file C:\Programme\nodejs\node_modules\npm\npmrc
>> 8 verbose exit [ 0, true ]
>> 9 error Error: Callback called more than once.
>> 9 error     at errorHandler
>> (C:\Programme\nodejs\node_modules\npm\lib\utils\error-handler.js:80:16)
>> 9 error     at list
>> (C:\Programme\nodejs\node_modules\npm\lib\config.js:295:3)
>> 9 error     at EventEmitter.config
>> (C:\Programme\nodejs\node_modules\npm\lib\config.js:55:36)
>> 9 error     at
>> Object.keys.concat.forEach.Object.defineProperty.get.commandCache.(anonymou s
>> function) (C:\Programme\nodejs\node_modules\npm\lib\npm.js:182:11)
>> 9 error     at EventEmitter.<anonymous>
>> (C:\Programme\nodejs\node_modules\npm\bin\npm-cli.js:84:28)
>> 9 error     at process.startup.processNextTick.process._tickCallback
>> (node.js:244:9)
>> 10 error If you need help, you may report this log at:
>> 10 error     <http://github.com/isaacs/npm/issues>
>> 10 error or email it to:
>> 10 error     <npm-@googlegroups.com>
>> 11 error System Windows_NT 5.1.2600
>> 12 error command "C:\\Programme\\nodejs\\\\node.exe"
>> "C:\\Programme\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "config" "list"
>> 13 error cwd H:\
>> 14 error node -v v0.8.3
>> 15 error npm -v 1.1.43
>> 16 verbose exit [ 1, true ]

> I hope you can help me.

> Some basic Infos:
> I'm using
> Windows XP
> Node v0.8.3
> npm v 1.1.43

> Cheers,

> It looks like your proxy is returning weird stuff.  Is there any way
> to get at the actual bytes it's sending?

> On Fri, Jul 27, 2012 at 3:21 AM, hbrockma <moorg...@googlemail.com> wrote:
>> Hey,

>> I got some trouble using node and the install from npm.

>> I want to make some documentation with YUI.
>> In order so to do I tried to install it with npm, but it gives me
>> Errormessages like the following, for everything I do with npm, like npm
>> search

>>> H:\>npm search yuidoc
>>> npm WARN Building the local index for the first time, please be patient
>>> npm http GET https://registry.npmjs.org/-/all
>>> npm http GET https://registry.npmjs.org/-/all
>>> npm http GET https://registry.npmjs.org/-/all
>>> npm ERR! Error: tunneling socket could not be established, cause=Parse
>>> Error
>>> npm ERR!     at ClientRequest.onError
>>> (C:\Programme\nodejs\node_modules\npm\node_modules\request\tunnel.js:161:17 )
>>> npm ERR!     at ClientRequest.g (events.js:185:14)
>>> npm ERR!     at ClientRequest.EventEmitter.emit (events.js:88:17)
>>> npm ERR!     at Socket.socketErrorListener (http.js:1320:9)
>>> npm ERR!     at Socket.EventEmitter.emit (events.js:88:17)
>>> npm ERR!     at Socket._destroy.self.errorEmitted (net.js:329:14)
>>> npm ERR!     at process.startup.processNextTick.process._tickCallback
>>> (node.js:244:9)
>>> 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 Windows_NT 5.1.2600
>>> npm ERR! command "C:\\Programme\\nodejs\\\\node.exe"
>>> "C:\\Programme\\nodejs\\nod
>>> e_modules\\npm\\bin\\npm-cli.js" "search" "yuidoc"
>>> npm ERR! cwd H:\
>>> npm ERR! node -v v0.8.3
>>> npm ERR! npm -v 1.1.43
>>> npm ERR! code ECONNRESET
>>> npm ERR!
>>> npm ERR! Additional logging details can be found in:
>>> npm ERR!     H:\npm-debug.log
>>> npm ERR! not ok code 0

>>> H:\>

>> I'm behind a corporate Proxy. I don't know if that helps. I already tried
>> npm config set proxy http://...

>> Plus when i try npm config list all i get is this (from npm-debug.log)

>>> 0 info it worked if it ends with ok
>>> 1 verbose cli [ 'C:\\Programme\\nodejs\\\\node.exe',
>>> 1 verbose cli
>>> 'C:\\Programme\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
>>> 1 verbose cli   'config',
>>> 1 verbose cli   'list' ]
>>> 2 info using n...@1.1.43
>>> 3 info using n...@v0.8.3
>>> 4 verbose node symlink C:\Programme\nodejs\\node.exe
>>> 5 verbose config file C:\Dokumente und Einstellungen\user\.npmrc
>>> 6 verbose config file C:\Programme\nodejs\etc\npmrc
>>> 7 verbose config file C:\Programme\nodejs\node_modules\npm\npmrc
>>> 8 verbose exit [ 0, true ]
>>> 9 error Error: Callback called more than once.
>>> 9 error     at errorHandler
>>> (C:\Programme\nodejs\node_modules\npm\lib\utils\error-handler.js:80:16)
>>> 9 error     at list
>>> (C:\Programme\nodejs\node_modules\npm\lib\config.js:295:3)
>>> 9 error     at EventEmitter.config
>>> (C:\Programme\nodejs\node_modules\npm\lib\config.js:55:36)
>>> 9 error     at
>>> Object.keys.concat.forEach.Object.defineProperty.get.commandCache.(anonymou s
>>> function) (C:\Programme\nodejs\node_modules\npm\lib\npm.js:182:11)
>>> 9 error     at EventEmitter.<anonymous>
>>> (C:\Programme\nodejs\node_modules\npm\bin\npm-cli.js:84:28)
>>> 9 error     at process.startup.processNextTick.process._tickCallback
>>> (node.js:244:9)
>>> 10 error If you need help, you may report this log at:
>>> 10 error     <http://github.com/isaacs/npm/issues>
>>> 10 error or email it to:
>>> 10 error     <npm-@googlegroups.com>
>>> 11 error System Windows_NT 5.1.2600
>>> 12 error command "C:\\Programme\\nodejs\\\\node.exe"
>>> "C:\\Programme\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "config" "list"
>>> 13 error cwd H:\
>>> 14 error node -v v0.8.3
>>> 15 error npm -v 1.1.43
>>> 16 verbose exit [ 1, true ]

>> I hope you can help me.

>> Some basic Infos:
>> I'm using
>> Windows XP
>> Node v0.8.3
>> npm v 1.1.43

>> Cheers,

> Callback issue fixed on 85f70a25514ff521bc5473ae4e4375fd93198c1c.

> On Fri, Jul 27, 2012 at 10:49 AM, Isaac Schlueter <i...@izs.me> wrote:
> > Yeah, the "callback called more than once" is indeed a bug.  But it
> > should still print out some stuff before that.

> > It looks like your proxy is returning weird stuff.  Is there any way
> > to get at the actual bytes it's sending?

> > On Fri, Jul 27, 2012 at 3:21 AM, hbrockma <moorg...@googlemail.com>
> wrote:
> >> Hey,

> >> I got some trouble using node and the install from npm.

> >> I want to make some documentation with YUI.
> >> In order so to do I tried to install it with npm, but it gives me
> >> Errormessages like the following, for everything I do with npm, like
> npm
> >> search

> >>> H:\>npm search yuidoc
> >>> npm WARN Building the local index for the first time, please be
> patient
> >>> npm http GET https://registry.npmjs.org/-/all
> >>> npm http GET https://registry.npmjs.org/-/all
> >>> npm http GET https://registry.npmjs.org/-/all
> >>> npm ERR! Error: tunneling socket could not be established, cause=Parse
> >>> Error
> >>> npm ERR!     at ClientRequest.onError

> (C:\Programme\nodejs\node_modules\npm\node_modules\request\tunnel.js:161:17 )

> >>> npm ERR!     at ClientRequest.g (events.js:185:14)
> >>> npm ERR!     at ClientRequest.EventEmitter.emit (events.js:88:17)
> >>> npm ERR!     at Socket.socketErrorListener (http.js:1320:9)
> >>> npm ERR!     at Socket.EventEmitter.emit (events.js:88:17)
> >>> npm ERR!     at Socket._destroy.self.errorEmitted (net.js:329:14)
> >>> npm ERR!     at process.startup.processNextTick.process._tickCallback
> >>> (node.js:244:9)
> >>> 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 Windows_NT 5.1.2600
> >>> npm ERR! command "C:\\Programme\\nodejs\\\\node.exe"
> >>> "C:\\Programme\\nodejs\\nod
> >>> e_modules\\npm\\bin\\npm-cli.js" "search" "yuidoc"
> >>> npm ERR! cwd H:\
> >>> npm ERR! node -v v0.8.3
> >>> npm ERR! npm -v 1.1.43
> >>> npm ERR! code ECONNRESET
> >>> npm ERR!
> >>> npm ERR! Additional logging details can be found in:
> >>> npm ERR!     H:\npm-debug.log
> >>> npm ERR! not ok code 0

> >>> H:\>

> >> I'm behind a corporate Proxy. I don't know if that helps. I already
> tried
> >> npm config set proxy http://...

> >> Plus when i try npm config list all i get is this (from npm-debug.log)

> >>> 0 info it worked if it ends with ok
> >>> 1 verbose cli [ 'C:\\Programme\\nodejs\\\\node.exe',
> >>> 1 verbose cli
> >>> 'C:\\Programme\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
> >>> 1 verbose cli   'config',
> >>> 1 verbose cli   'list' ]
> >>> 2 info using n...@1.1.43
> >>> 3 info using n...@v0.8.3
> >>> 4 verbose node symlink C:\Programme\nodejs\\node.exe
> >>> 5 verbose config file C:\Dokumente und Einstellungen\user\.npmrc
> >>> 6 verbose config file C:\Programme\nodejs\etc\npmrc
> >>> 7 verbose config file C:\Programme\nodejs\node_modules\npm\npmrc
> >>> 8 verbose exit [ 0, true ]
> >>> 9 error Error: Callback called more than once.
> >>> 9 error     at errorHandler

> (C:\Programme\nodejs\node_modules\npm\lib\utils\error-handler.js:80:16)
> >>> 9 error     at list
> >>> (C:\Programme\nodejs\node_modules\npm\lib\config.js:295:3)
> >>> 9 error     at EventEmitter.config
> >>> (C:\Programme\nodejs\node_modules\npm\lib\config.js:55:36)
> >>> 9 error     at

> Object.keys.concat.forEach.Object.defineProperty.get.commandCache.(anonymou s

> >>> function) (C:\Programme\nodejs\node_modules\npm\lib\npm.js:182:11)
> >>> 9 error     at EventEmitter.<anonymous>
> >>> (C:\Programme\nodejs\node_modules\npm\bin\npm-cli.js:84:28)
> >>> 9 error     at process.startup.processNextTick.process._tickCallback
> >>> (node.js:244:9)
> >>> 10 error If you need help, you may report this log at:
> >>> 10 error     <http://github.com/isaacs/npm/issues>
> >>> 10 error or email it to:
> >>> 10 error     <npm-@googlegroups.com>
> >>> 11 error System Windows_NT 5.1.2600
> >>> 12 error command "C:\\Programme\\nodejs\\\\node.exe"
> >>> "C:\\Programme\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "config"
> "list"
> >>> 13 error cwd H:\
> >>> 14 error node -v v0.8.3
> >>> 15 error npm -v 1.1.43
> >>> 16 verbose exit [ 1, true ]

> >> I hope you can help me.

> >> Some basic Infos:
> >> I'm using
> >> Windows XP
> >> Node v0.8.3
> >> npm v 1.1.43

> >> Cheers,

> Am Montag, 30. Juli 2012 10:42:36 UTC+2 schrieb hbrockma:

>> Okay.
>> Got my Proxy-problems solved.
>> Now I got some new problems.

>>> H:\>npm install yui
>>> npm http GET https://registry.npmjs.org/yui
>>> npm http 304 https://registry.npmjs.org/yui
>>> npm http GET https://registry.npmjs.org/yui/-/yui-3.5.1-2.tgz
>>> npm ERR! fetch failed https://registry.npmjs.org/yui/-/yui-3.5.1-2.tgz
>>> npm http GET https://registry.npmjs.org/yui/-/yui-3.5.1-2.tgz
>>> npm ERR! fetch failed https://registry.npmjs.org/yui/-/yui-3.5.1-2.tgz
>>> npm http GET https://registry.npmjs.org/yui/-/yui-3.5.1-2.tgz
>>> npm ERR! fetch failed https://registry.npmjs.org/yui/-/yui-3.5.1-2.tgz

>> But I try to find a solution. I think this topic can be closed.

>> Am Freitag, 27. Juli 2012 19:50:56 UTC+2 schrieb Isaac Schlueter:

>>> Callback issue fixed on 85f70a25514ff521bc5473ae4e4375fd93198c1c.

>>> On Fri, Jul 27, 2012 at 10:49 AM, Isaac Schlueter <i...@izs.me> wrote:
>>> > Yeah, the "callback called more than once" is indeed a bug.  But it
>>> > should still print out some stuff before that.

>>> > It looks like your proxy is returning weird stuff.  Is there any way
>>> > to get at the actual bytes it's sending?

>>> > On Fri, Jul 27, 2012 at 3:21 AM, hbrockma <moorg...@googlemail.com>
>>> > wrote:
>>> >> Hey,

>>> >> I got some trouble using node and the install from npm.

>>> >> I want to make some documentation with YUI.
>>> >> In order so to do I tried to install it with npm, but it gives me
>>> >> Errormessages like the following, for everything I do with npm, like
>>> >> npm
>>> >> search

>>> >>> H:\>npm search yuidoc
>>> >>> npm WARN Building the local index for the first time, please be
>>> >>> patient
>>> >>> npm http GET https://registry.npmjs.org/-/all
>>> >>> npm http GET https://registry.npmjs.org/-/all
>>> >>> npm http GET https://registry.npmjs.org/-/all
>>> >>> npm ERR! Error: tunneling socket could not be established,
>>> >>> cause=Parse
>>> >>> Error
>>> >>> npm ERR!     at ClientRequest.onError

>>> >>> (C:\Programme\nodejs\node_modules\npm\node_modules\request\tunnel.js:161:17 )
>>> >>> npm ERR!     at ClientRequest.g (events.js:185:14)
>>> >>> npm ERR!     at ClientRequest.EventEmitter.emit (events.js:88:17)
>>> >>> npm ERR!     at Socket.socketErrorListener (http.js:1320:9)
>>> >>> npm ERR!     at Socket.EventEmitter.emit (events.js:88:17)
>>> >>> npm ERR!     at Socket._destroy.self.errorEmitted (net.js:329:14)
>>> >>> npm ERR!     at process.startup.processNextTick.process._tickCallback
>>> >>> (node.js:244:9)
>>> >>> 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 Windows_NT 5.1.2600
>>> >>> npm ERR! command "C:\\Programme\\nodejs\\\\node.exe"
>>> >>> "C:\\Programme\\nodejs\\nod
>>> >>> e_modules\\npm\\bin\\npm-cli.js" "search" "yuidoc"
>>> >>> npm ERR! cwd H:\
>>> >>> npm ERR! node -v v0.8.3
>>> >>> npm ERR! npm -v 1.1.43
>>> >>> npm ERR! code ECONNRESET
>>> >>> npm ERR!
>>> >>> npm ERR! Additional logging details can be found in:
>>> >>> npm ERR!     H:\npm-debug.log
>>> >>> npm ERR! not ok code 0

>>> >>> H:\>

>>> >> I'm behind a corporate Proxy. I don't know if that helps. I already
>>> >> tried
>>> >> npm config set proxy http://...

>>> >> Plus when i try npm config list all i get is this (from npm-debug.log)

>>> >>> 0 info it worked if it ends with ok
>>> >>> 1 verbose cli [ 'C:\\Programme\\nodejs\\\\node.exe',
>>> >>> 1 verbose cli
>>> >>> 'C:\\Programme\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
>>> >>> 1 verbose cli   'config',
>>> >>> 1 verbose cli   'list' ]
>>> >>> 2 info using n...@1.1.43
>>> >>> 3 info using n...@v0.8.3
>>> >>> 4 verbose node symlink C:\Programme\nodejs\\node.exe
>>> >>> 5 verbose config file C:\Dokumente und Einstellungen\user\.npmrc
>>> >>> 6 verbose config file C:\Programme\nodejs\etc\npmrc
>>> >>> 7 verbose config file C:\Programme\nodejs\node_modules\npm\npmrc
>>> >>> 8 verbose exit [ 0, true ]
>>> >>> 9 error Error: Callback called more than once.
>>> >>> 9 error     at errorHandler

>>> >>> (C:\Programme\nodejs\node_modules\npm\lib\utils\error-handler.js:80:16)
>>> >>> 9 error     at list
>>> >>> (C:\Programme\nodejs\node_modules\npm\lib\config.js:295:3)
>>> >>> 9 error     at EventEmitter.config
>>> >>> (C:\Programme\nodejs\node_modules\npm\lib\config.js:55:36)
>>> >>> 9 error     at

>>> >>> Object.keys.concat.forEach.Object.defineProperty.get.commandCache.(anonymou s
>>> >>> function) (C:\Programme\nodejs\node_modules\npm\lib\npm.js:182:11)
>>> >>> 9 error     at EventEmitter.<anonymous>
>>> >>> (C:\Programme\nodejs\node_modules\npm\bin\npm-cli.js:84:28)
>>> >>> 9 error     at process.startup.processNextTick.process._tickCallback
>>> >>> (node.js:244:9)
>>> >>> 10 error If you need help, you may report this log at:
>>> >>> 10 error     <http://github.com/isaacs/npm/issues>
>>> >>> 10 error or email it to:
>>> >>> 10 error     <npm-@googlegroups.com>
>>> >>> 11 error System Windows_NT 5.1.2600
>>> >>> 12 error command "C:\\Programme\\nodejs\\\\node.exe"
>>> >>> "C:\\Programme\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "config"
>>> >>> "list"
>>> >>> 13 error cwd H:\
>>> >>> 14 error node -v v0.8.3
>>> >>> 15 error npm -v 1.1.43
>>> >>> 16 verbose exit [ 1, true ]

>>> >> I hope you can help me.

>>> >> Some basic Infos:
>>> >> I'm using
>>> >> Windows XP
>>> >> Node v0.8.3
>>> >> npm v 1.1.43

>>> >> Cheers,

> Okay.
> Got my Proxy-problems solved.
> Now I got some new problems.

>> *H:\>npm install yui*
>> *npm http GET https://registry.npmjs.org/yui*
>> *npm http 304 https://registry.npmjs.org/yui*
>> *npm http GET https://registry.npmjs.org/yui/-/yui-3.5.1-2.tgz*
>> *npm ERR! fetch failed https://registry.npmjs.org/yui/-/yui-3.5.1-2.tgz*
>> *npm http GET https://registry.npmjs.org/yui/-/yui-3.5.1-2.tgz*
>> *npm ERR! fetch failed https://registry.npmjs.org/yui/-/yui-3.5.1-2.tgz*
>> *npm http GET https://registry.npmjs.org/yui/-/yui-3.5.1-2.tgz*
>> *npm ERR! fetch failed https://registry.npmjs.org/yui/-/yui-3.5.1-2.tgz*

> But I try to find a solution. I think this topic can be closed.

> Am Freitag, 27. Juli 2012 19:50:56 UTC+2 schrieb Isaac Schlueter:

>> Callback issue fixed on 85f70a25514ff521bc5473ae4e4375fd93198c1c.

>> On Fri, Jul 27, 2012 at 10:49 AM, Isaac Schlueter <i...@izs.me<javascript:>>
>> wrote:
>> > Yeah, the "callback called more than once" is indeed a bug.  But it
>> > should still print out some stuff before that.

>> > It looks like your proxy is returning weird stuff.  Is there any way
>> > to get at the actual bytes it's sending?

>> > On Fri, Jul 27, 2012 at 3:21 AM, hbrockma <moor...@googlemail.com<javascript:>>
>> wrote:
>> >> Hey,

>> >> I got some trouble using node and the install from npm.

>> >> I want to make some documentation with YUI.
>> >> In order so to do I tried to install it with npm, but it gives me
>> >> Errormessages like the following, for everything I do with npm, like
>> npm
>> >> search

>> >>> H:\>npm search yuidoc
>> >>> npm WARN Building the local index for the first time, please be
>> patient
>> >>> npm http GET https://registry.npmjs.org/-/all
>> >>> npm http GET https://registry.npmjs.org/-/all
>> >>> npm http GET https://registry.npmjs.org/-/all
>> >>> npm ERR! Error: tunneling socket could not be established,
>> cause=Parse
>> >>> Error
>> >>> npm ERR!     at ClientRequest.onError

>> (C:\Programme\nodejs\node_modules\npm\node_modules\request\tunnel.js:161:17 )

>> >>> npm ERR!     at ClientRequest.g (events.js:185:14)
>> >>> npm ERR!     at ClientRequest.EventEmitter.emit (events.js:88:17)
>> >>> npm ERR!     at Socket.socketErrorListener (http.js:1320:9)
>> >>> npm ERR!     at Socket.EventEmitter.emit (events.js:88:17)
>> >>> npm ERR!     at Socket._destroy.self.errorEmitted (net.js:329:14)
>> >>> npm ERR!     at process.startup.processNextTick.process._tickCallback
>> >>> (node.js:244:9)
>> >>> 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!     <np...@googlegroups.com <javascript:>>

>> >>> npm ERR! System Windows_NT 5.1.2600
>> >>> npm ERR! command "C:\\Programme\\nodejs\\\\node.exe"
>> >>> "C:\\Programme\\nodejs\\nod
>> >>> e_modules\\npm\\bin\\npm-cli.js" "search" "yuidoc"
>> >>> npm ERR! cwd H:\
>> >>> npm ERR! node -v v0.8.3
>> >>> npm ERR! npm -v 1.1.43
>> >>> npm ERR! code ECONNRESET
>> >>> npm ERR!
>> >>> npm ERR! Additional logging details can be found in:
>> >>> npm ERR!     H:\npm-debug.log
>> >>> npm ERR! not ok code 0

>> >>> H:\>

>> >> I'm behind a corporate Proxy. I don't know if that helps. I already
>> tried
>> >> npm config set proxy http://...

>> >> Plus when i try npm config list all i get is this (from npm-debug.log)

>> >>> 0 info it worked if it ends with ok
>> >>> 1 verbose cli [ 'C:\\Programme\\nodejs\\\\node.exe',
>> >>> 1 verbose cli
>> >>> 'C:\\Programme\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
>> >>> 1 verbose cli   'config',
>> >>> 1 verbose cli   'list' ]
>> >>> 2 info using n...@1.1.43
>> >>> 3 info using n...@v0.8.3
>> >>> 4 verbose node symlink C:\Programme\nodejs\\node.exe
>> >>> 5 verbose config file C:\Dokumente und Einstellungen\user\.npmrc
>> >>> 6 verbose config file C:\Programme\nodejs\etc\npmrc
>> >>> 7 verbose config file C:\Programme\nodejs\node_modules\npm\npmrc
>> >>> 8 verbose exit [ 0, true ]
>> >>> 9 error Error: Callback called more than once.
>> >>> 9 error     at errorHandler

>> (C:\Programme\nodejs\node_modules\npm\lib\utils\error-handler.js:80:16)
>> >>> 9 error     at list
>> >>> (C:\Programme\nodejs\node_modules\npm\lib\config.js:295:3)
>> >>> 9 error     at EventEmitter.config
>> >>> (C:\Programme\nodejs\node_modules\npm\lib\config.js:55:36)
>> >>> 9 error     at

>> Object.keys.concat.forEach.Object.defineProperty.get.commandCache.(anonymou s

>> >>> function) (C:\Programme\nodejs\node_modules\npm\lib\npm.js:182:11)
>> >>> 9 error     at EventEmitter.<anonymous>
>> >>> (C:\Programme\nodejs\node_modules\npm\bin\npm-cli.js:84:28)
>> >>> 9 error     at process.startup.processNextTick.process._tickCallback
>> >>> (node.js:244:9)
>> >>> 10 error If you need help, you may report this log at:
>> >>> 10 error     <http://github.com/isaacs/npm/issues>
>> >>> 10 error or email it to:
>> >>> 10 error     <np...@googlegroups.com <javascript:>>
>> >>> 11 error System Windows_NT 5.1.2600
>> >>> 12 error command "C:\\Programme\\nodejs\\\\node.exe"
>> >>> "C:\\Programme\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "config"
>> "list"
>> >>> 13 error cwd H:\
>> >>> 14 error node -v v0.8.3
>> >>> 15 error npm -v 1.1.43
>> >>> 16 verbose exit [ 1, true ]

>> >> I hope you can help me.

>> >> Some basic Infos:
>> >> I'm using
>> >> Windows XP
>> >> Node v0.8.3
>> >> npm v 1.1.43

>> >> Cheers,