-
Notifications
You must be signed in to change notification settings - Fork 46.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
React-tools installation fails #3660
Comments
I was logged in with administrator privileges |
Looks like this is a permissions error. This sounds like an issue to take up with npm. |
I successfully installed using the Administrator. before i use other windows accounts failure. ths guys |
This was referenced Aug 18, 2021
This was referenced Sep 12, 2021
This was referenced May 13, 2022
This was referenced Nov 27, 2023
This was referenced Mar 22, 2024
This was referenced May 13, 2024
This was referenced May 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
npm-debug.log
/////////////////////////////////////
0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'install',
1 verbose cli '-g',
1 verbose cli 'react-tools' ]
2 info using npm@2.7.4
3 info using node@v0.12.2
4 verbose node symlink C:\Program Files\nodejs\node.exe
5 silly cache add args [ 'react-tools', null ]
6 verbose cache add spec react-tools
7 silly cache add parsed spec { raw: 'react-tools',
7 silly cache add scope: null,
7 silly cache add name: 'react-tools',
7 silly cache add rawSpec: '',
7 silly cache add spec: '',
7 silly cache add type: 'range' }
8 verbose addNamed react-tools@
9 silly addNamed semver.valid null
10 silly addNamed semver.validRange *
11 silly addNameRange { name: 'react-tools', range: '*', hasData: false }
12 silly mapToRegistry name react-tools
13 silly mapToRegistry using default registry
14 silly mapToRegistry registry https://registry.npmjs.org/
15 silly mapToRegistry uri https://registry.npmjs.org/react-tools
16 verbose addNameRange registry:https://registry.npmjs.org/react-tools not in flight; fetching
17 verbose request uri https://registry.npmjs.org/react-tools
18 verbose request no auth needed
19 info attempt registry request try #1 at 19:08:18
20 verbose request id 5b79c264902ebbf2
21 http request GET https://registry.npmjs.org/react-tools
22 info retry will retry, error on last attempt: Error: connect EACCES
23 info attempt registry request try #2 at 19:08:29
24 http request GET https://registry.npmjs.org/react-tools
25 info retry will retry, error on last attempt: Error: connect EACCES
26 info attempt registry request try #3 at 19:09:29
27 http request GET https://registry.npmjs.org/react-tools
28 verbose stack Error: connect EACCES
28 verbose stack at exports._errnoException (util.js:746:11)
28 verbose stack at TCPConnectWrap.afterConnect as oncomplete
29 verbose cwd C:\Windows\System32
30 error Windows_NT 6.1.7601
31 error argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "-g" "react-tools"
32 error node v0.12.2
33 error npm v2.7.4
34 error code EACCES
35 error errno EACCES
36 error syscall connect
37 error Error: connect EACCES
37 error at exports._errnoException (util.js:746:11)
37 error at TCPConnectWrap.afterConnect as oncomplete
37 error { [Error: connect EACCES] code: 'EACCES', errno: 'EACCES', syscall: 'connect' }
38 error Please try running this command again as root/Administrator.
39 verbose exit [ 1, true ]
tks~:)
The text was updated successfully, but these errors were encountered: