Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Error installing testacular with Node.js v 0.10.1 on Win 7 64 bit #3284

Closed
zeamir opened this Issue Mar 25, 2013 · 1 comment

Comments

Projects
None yet
2 participants

zeamir commented Mar 25, 2013

Hello,
I get the following error when tyring to install testacular using "npm install -g testacular".
Here is the log file...
Is this a known issue?

here is the npm-debug.log

4728 silly addNameRange '0.9.8',
4728 silly addNameRange '0.9.9',
4728 silly addNameRange '1.0.0',
4728 silly addNameRange '1.0.1',
4728 silly addNameRange '1.0.2' ] ]
4729 verbose addNamed [ 'esprima', '1.0.2' ]
4730 verbose addNamed [ '1.0.2', '1.0.2' ]
4731 silly lockFile a839e9a7-esprima-1-0-2 esprima@1.0.2
4732 verbose lock esprima@1.0.2 C:\Users\zahavia\AppData\Roaming\npm-cache\a839e9a7-esprima-1-0-2.lock
4733 verbose url raw estraverse
4734 verbose url resolving [ 'https://registry.npmjs.org/', './estraverse' ]
4735 verbose url resolved https://registry.npmjs.org/estraverse
4736 info trying registry request attempt 1 at 22:03:04
4737 verbose etag "7BIAMU9WBX63QNXWKLIJD6MCH"
4738 http GET https://registry.npmjs.org/estraverse
4739 error Error: read ECONNRESET
4739 error at errnoException (net.js:878:11)
4739 error at TCP.onread (net.js:539:19)
4740 error If you need help, you may report this log at:
4740 error http://github.com/isaacs/npm/issues
4740 error or email it to:
4740 error npm-@googlegroups.com
4741 error System Windows_NT 6.1.7601
4742 error command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "-g" "testacular"
4743 error cwd C:\Users\zahavia
4744 error node -v v0.10.1
4745 error npm -v 1.2.15
4746 error syscall read
4747 error code ECONNRESET
4748 error errno ECONNRESET
4749 verbose exit [ 1, true ]

Member

mfncooper commented Mar 26, 2013

That looks like a network connectivity issue, not an npm issue. If you're behind a firewall, make sure you have proxy and / or https-proxy configured appropriately. See npm help config.

@mfncooper mfncooper closed this Mar 26, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment