angular-cli: When install angular cli stuck

Please provide us with the following information:

OS? Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?) windows 10

Versions. Please run ng --version. If there’s nothing outputted, please run in a Terminal: node --version And paste the result here. node version v6.2.2
Repro steps. Was this an app that wasn’t created using the CLI? What change did you do on your code? etc.
The log given by the failure. Normally this include a stack trace and some more information.
Mention any other details that might be useful.

Thanks! We’ll be in touch soon.

when i try to install angular cli in my computer i keep stuck on

loadRequestedDeps ->netw | #######---------------------------------

and not going any where, i’m running the command prompt in administrator already

and i’m already try this step

npm uninstall -g angular-cli
npm cache clean
npm install -g angular-cli@latest

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 22 (3 by maintainers)

Most upvoted comments

$ npm install -g @angular/cli C:\Users\Kv\AppData\Roaming\npm\ng -> C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\bin\ng

node-sass@4.5.3 install C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\node-sass node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.5.3/win32-x64-51_binding.node Cannot download “https://github.com/sass/node-sass/releases/download/v4.5.3/win32-x64-51_binding.node”:

ESOCKETTIMEDOUT

Hint: If github.com is not accessible in your location try setting a proxy via HTTP_PROXY, e.g.

  export HTTP_PROXY=http://example.com:1234

or configure npm proxy via

  npm config set proxy http://example.com:8080

node-sass@4.5.3 postinstall C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\node-sass node scripts/build.js

Binary found at C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\node-sass\vendor\win32-x64-51\binding.node Testing binary Binary has a problem: Error: %1 is not a valid Win32 application. \?\C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\node-sass\vendor\win32-x64-51\binding.node at Object.Module._extensions…node (module.js:598:18) at Module.load (module.js:488:32) at tryModuleLoad (module.js:447:12) at Function.Module._load (module.js:439:3) at Module.require (module.js:498:17) at require (internal/module.js:20:19) at module.exports (C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\node-sass\lib\binding.js:19:10) at Object.<anonymous> (C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\node-sass\lib\index.js:14:35) at Module._compile (module.js:571:32) at Object.Module._extensions…js (module.js:580:10) Building the binary locally Building: C:\Program Files\nodejs\node.exe C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\node-gyp\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library= gyp info it worked if it ends with ok gyp verb cli [ ‘C:\Program Files\nodejs\node.exe’, gyp verb cli ‘C:\Users\Kv\AppData\Roaming\npm\node_modules\@angular\cli\node_modules\node-gyp\bin\node-gyp.js’, gyp verb cli ‘rebuild’, gyp verb cli ‘–verbose’, gyp verb cli ‘–libsass_ext=’, gyp verb cli ‘–libsass_cflags=’, gyp verb cli ‘–libsass_ldflags=’, gyp verb cli ‘–libsass_library=’ ] gyp info using node-gyp@3.6.1 gyp info using node@7.7.4 | win32 | x64 gyp verb command rebuild [] gyp verb command clean [] gyp verb clean removing “build” directory gyp verb command configure [] gyp verb check python checking for Python executable “python2” in the PATH gyp verb which failed Error: not found: python2 gyp verb which failed at getNotFoundError (C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\which\which.js:13:12) gyp verb which failed at F (C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\which\which.js:68:19) gyp verb which failed at E (C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\which\which.js:80:29) gyp verb which failed at C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\which\which.js:89:16 gyp verb which failed at C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\isexe\index.js:42:5 gyp verb which failed at C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\isexe\windows.js:36:5 gyp verb which failed at FSReqWrap.oncomplete (fs.js:114:15) gyp verb which failed python2 { Error: not found: python2 gyp verb which failed at getNotFoundError (C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\which\which.js:13:12) gyp verb which failed at F (C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\which\which.js:68:19) gyp verb which failed at E (C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\which\which.js:80:29) gyp verb which failed at C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\which\which.js:89:16 gyp verb which failed at C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\isexe\index.js:42:5 gyp verb which failed at C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\isexe\windows.js:36:5 gyp verb which failed at FSReqWrap.oncomplete (fs.js:114:15) code: ‘ENOENT’ } gyp verb check python checking for Python executable “python” in the PATH gyp verb which failed Error: not found: python gyp verb which failed at getNotFoundError (C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\which\which.js:13:12) gyp verb which failed at F (C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\which\which.js:68:19) gyp verb which failed at E (C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\which\which.js:80:29) gyp verb which failed at C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\which\which.js:89:16 gyp verb which failed at C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\isexe\index.js:42:5 gyp verb which failed at C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\isexe\windows.js:36:5 gyp verb which failed at FSReqWrap.oncomplete (fs.js:114:15) gyp verb which failed python { Error: not found: python gyp verb which failed at getNotFoundError (C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\which\which.js:13:12) gyp verb which failed at F (C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\which\which.js:68:19) gyp verb which failed at E (C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\which\which.js:80:29) gyp verb which failed at C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\which\which.js:89:16 gyp verb which failed at C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\isexe\index.js:42:5 gyp verb which failed at C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\isexe\windows.js:36:5 gyp verb which failed at FSReqWrap.oncomplete (fs.js:114:15) code: ‘ENOENT’ } gyp verb could not find “python”. checking python launcher gyp verb could not find “python”. guessing location gyp verb ensuring that file exists: C:\Python27\python.exe gyp ERR! configure error gyp ERR! stack Error: Can’t find Python executable “python”, you can set the PYTHON env variable. gyp ERR! stack at PythonFinder.failNoPython (C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\node-gyp\lib\configure.js:483:19) gyp ERR! stack at PythonFinder.<anonymous> (C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\node-gyp\lib\configure.js:508:16) gyp ERR! stack at C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\graceful-fs\polyfills.js:284:29 gyp ERR! stack at FSReqWrap.oncomplete (fs.js:114:15) gyp ERR! System Windows_NT 10.0.14393 gyp ERR! command “C:\Program Files\nodejs\node.exe” “C:\Users\Kv\AppData\Roaming\npm\node_modules\@angular\cli\node_modules\node-gyp\bin\node-gyp.js” “rebuild” “–verbose” “–libsass_ext=” “–libsass_cflags=” “–libsass_ldflags=” “–libsass_library=” gyp ERR! cwd C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\node-sass gyp ERR! node -v v7.7.4 gyp ERR! node-gyp -v v3.6.1 gyp ERR! not ok Build failed with error code: 1 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules@angular\cli\node_modules\chokidar\node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.1: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“win32”,“arch”:“x64”}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: node-sass@4.5.3 (node_modules@angular\cli\node_modules\node-sass): npm WARN optional SKIPPING OPTIONAL DEPENDENCY: node-sass@4.5.3 postinstall: node scripts/build.js npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1 npm ERR! Windows_NT 10.0.14393 npm ERR! argv “C:\Program Files\nodejs\node.exe” “C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js” “install” “-g” “@angular/cli” npm ERR! node v7.7.4 npm ERR! npm v4.1.2 npm ERR! path C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\globule\node_modules npm ERR! code EPERM npm ERR! errno -4048 npm ERR! syscall scandir

npm ERR! Error: EPERM: operation not permitted, scandir ‘C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\globule\node_modules’ npm ERR! { Error: EPERM: operation not permitted, scandir ‘C:\Users\Kv\AppData\Roaming\npm\node_modules@angular\cli\node_modules\globule\node_modules’ npm ERR! errno: -4048, npm ERR! code: ‘EPERM’, npm ERR! syscall: ‘scandir’, npm ERR! path: ‘C:\Users\Kv\AppData\Roaming\npm\node_modules\@angular\cli\node_modules\globule\node_modules’ } npm ERR! npm ERR! Please try running this command again as root/Administrator.

npm ERR! Please include the following file with any support request: npm ERR! C:\Users\Kv\Desktop\npm-debug.log

karnavpargi on May 29, 2017

Closing as old and because original poster never came back to the issue. There are other problems in this thread, but if you’re still having them please open new issues.

@albertodominguezs see https://docs.npmjs.com/getting-started/fixing-npm-permissions

filipesilva on Oct 23, 2016