Error installing package (force or no force)

[DoomerDGR8]

OS?

Windows 10 Enterprise x64 v1604-14942.1000

Versions.

node: v6.8.1
npm: v3.10.7 (reverted from v3.10.8 due to npm/npm#14042)
np: N/A (cannot install)

The log given by the failure.

PS E:\web\ang2-qs> npm install -g -f angular-cli
npm WARN using --force I sure hope you know what you are doing.
npm WARN addRemoteGit Error: Command failed: git -c core.longpaths=true config --get remote.origin.url
npm WARN addRemoteGit
npm WARN addRemoteGit     at ChildProcess.exithandler (child_process.js:206:12)
npm WARN addRemoteGit     at emitTwo (events.js:106:13)
npm WARN addRemoteGit     at ChildProcess.emit (events.js:191:7)
npm WARN addRemoteGit     at maybeClose (internal/child_process.js:877:16)
npm WARN addRemoteGit     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
npm WARN addRemoteGit  webpack/compression-webpack-plugin#7e55907cd54a2e91b96d25a660acc6a2a6453f54 resetting remote D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-ec76b2fe because of error: { Error: Command failed: git -c core.longpaths=true config --get remote.origin.url
npm WARN addRemoteGit
npm WARN addRemoteGit     at ChildProcess.exithandler (child_process.js:206:12)
npm WARN addRemoteGit     at emitTwo (events.js:106:13)
npm WARN addRemoteGit     at ChildProcess.emit (events.js:191:7)
npm WARN addRemoteGit     at maybeClose (internal/child_process.js:877:16)
npm WARN addRemoteGit     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
npm WARN addRemoteGit   killed: false,
npm WARN addRemoteGit   code: 1,
npm WARN addRemoteGit   signal: null,
npm WARN addRemoteGit   cmd: 'git -c core.longpaths=true config --get remote.origin.url' }
npm ERR! git clone --template=D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\_templates --mirror git://github.com/webpack/compression-webpack-plugin.git D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e559
07cd54a2e91b96d25a660acc6a2a6453f54-ec76b2fe: Cloning into bare repository 'D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-ec76b2fe'...
npm ERR! git clone --template=D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\_templates --mirror git://github.com/webpack/compression-webpack-plugin.git D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e559
07cd54a2e91b96d25a660acc6a2a6453f54-ec76b2fe: fatal: unable to connect to github.com:
npm ERR! git clone --template=D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\_templates --mirror git://github.com/webpack/compression-webpack-plugin.git D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e559
07cd54a2e91b96d25a660acc6a2a6453f54-ec76b2fe: github.com[0: 192.30.253.112]: errno=Invalid argument
npm ERR! git clone D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-https-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-541c96f3 D:\Users\6587\AppData\Local\Temp\npm-11244-6ae584f0\git-cache-16504c54\7e55907cd54a2e91b9
6d25a660acc6a2a6453f54: Cloning into 'D:\Users\6587\AppData\Local\Temp\npm-11244-6ae584f0\git-cache-16504c54\7e55907cd54a2e91b96d25a660acc6a2a6453f54'...
npm ERR! git clone D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-https-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-541c96f3 D:\Users\6587\AppData\Local\Temp\npm-11244-6ae584f0\git-cache-16504c54\7e55907cd54a2e91b9
6d25a660acc6a2a6453f54: error: cannot spawn sh: No such file or directory
npm ERR! git clone D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-https-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-541c96f3 D:\Users\6587\AppData\Local\Temp\npm-11244-6ae584f0\git-cache-16504c54\7e55907cd54a2e91b9
6d25a660acc6a2a6453f54: fatal: unable to fork
npm ERR! git clone D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-https-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-541c96f3 D:\Users\6587\AppData\Local\Temp\npm-11244-6ae584f0\git-cache-16504c54\7e55907cd54a2e91b9
6d25a660acc6a2a6453f54:
npm WARN addRemoteGit Error: Command failed: git -c core.longpaths=true config --get remote.origin.url
npm WARN addRemoteGit
npm WARN addRemoteGit     at ChildProcess.exithandler (child_process.js:206:12)
npm WARN addRemoteGit     at emitTwo (events.js:106:13)
npm WARN addRemoteGit     at ChildProcess.emit (events.js:191:7)
npm WARN addRemoteGit     at maybeClose (internal/child_process.js:877:16)
npm WARN addRemoteGit     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
npm WARN addRemoteGit  webpack/compression-webpack-plugin#7e55907cd54a2e91b96d25a660acc6a2a6453f54 resetting remote D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-e286d0b
5 because of error: { Error: Command failed: git -c core.longpaths=true config --get remote.origin.url
npm WARN addRemoteGit
npm WARN addRemoteGit     at ChildProcess.exithandler (child_process.js:206:12)
npm WARN addRemoteGit     at emitTwo (events.js:106:13)
npm WARN addRemoteGit     at ChildProcess.emit (events.js:191:7)
npm WARN addRemoteGit     at maybeClose (internal/child_process.js:877:16)
npm WARN addRemoteGit     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
npm WARN addRemoteGit   killed: false,
npm WARN addRemoteGit   code: 1,
npm WARN addRemoteGit   signal: null,
npm WARN addRemoteGit   cmd: 'git -c core.longpaths=true config --get remote.origin.url' }
npm ERR! git clone --template=D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\_templates --mirror git@github.com:webpack/compression-webpack-plugin.git D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907
cd54a2e91b96d25a660acc6a2a6453f54-e286d0b5: Cloning into bare repository 'D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-e286d0b5'...
npm ERR! git clone --template=D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\_templates --mirror git@github.com:webpack/compression-webpack-plugin.git D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907
cd54a2e91b96d25a660acc6a2a6453f54-e286d0b5: error: cannot spawn ssh: No such file or directory
npm ERR! git clone --template=D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\_templates --mirror git@github.com:webpack/compression-webpack-plugin.git D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907
cd54a2e91b96d25a660acc6a2a6453f54-e286d0b5: fatal: unable to fork
npm ERR! Windows_NT 10.0.14942
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "D:\\Users\\6587\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "-f" "angular-cli"
npm ERR! node v6.8.1
npm ERR! npm  v3.10.7
npm ERR! code 128

npm ERR! Command failed: git -c core.longpaths=true clone --template=D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\_templates --mirror git@github.com:webpack/compression-webpack-plugin.git D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack
-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-e286d0b5
npm ERR! Cloning into bare repository 'D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-e286d0b5'...
npm ERR! error: cannot spawn ssh: No such file or directory
npm ERR! fatal: unable to fork
npm ERR!
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     E:\web\ang2-qs\npm-debug.log

[Meligy]

Hmm..

Since you are using Enterprise Windows, I guess you are behind a proxy (and probably one that requires authentication).

If so, I think this issue is a duplicate of #2685, which is basically that the install gets some packages from git, and your git is not configurated to use the proxy correctly (for example, you cannot clone from github).

If this is the case, you may close this issue, and:

• Update your git proxy settings (I have some tips that might help in the other issue), your passing test is being able to clone from github from command prompt
• Or: disable proxy and joining a network that doesn't required it, temporarily of course, and back when done
• And close this issue, and subscribe to ERROR when trying to run ng new when behind a corporate proxy #2685 (subscribe link at the bottom right), since it seems the team is changing the github dependencies to npm registry ones, and then you can get notified as soon as this is complete

Cheers,

[DoomerDGR8]

I'm pretty sure there is no proxy in our environment.

[Meligy]

Do you have git installed and in the environment path?

Are you able to run something like git clone https://github.com/test/HelloWorld in the same folder?

[DoomerDGR8]

Yes. I'm able to clone fine. And as per my pasted log above, the issue arises from 'webpack/compression-webpack-plugin' which is consistent with #2685 however, my project.json doesn't include that reference.

[Meligy]

Alright, here's something different to try:

npm rm -g angular-cli
npm cache clear
npm i -g angular-cli --no-optional

These are the official upgrade instructions, which may work for your install as well.

Except for the --no-optional flag, which is just something I have found to help on Windows when random packages fail to install sometimes.

Another flag that seems to help is msvs_version=2015 (replace 2015 with the version of Visual Studio you have, or do not bother with the parameter at all if you don't have any installed).

And yes, ensure you are running command prompt as admin. sometimes you get NPM issues without that.

Let me know how it goes.

Cheers,

[DoomerDGR8]

No luck. Here is what I get:

C:\WINDOWS\system32>npm rm -g angular-cli

C:\WINDOWS\system32>npm cache clear

C:\WINDOWS\system32>npm i -g angular-cli --no-optional
npm ERR! git clone D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-https-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-541c96f3 D:\Users\6587\AppData\Local\Temp\npm-12540-fcf54521\git-cache-1126e2b1\7e55907cd54a2e91b96d25a660acc6a2a6453f54: Cloning into 'D:\Users\6587\AppData\Local\Temp\npm-12540-fcf54521\git-cache-1126e2b1\7e55907cd54a2e91b96d25a660acc6a2a6453f54'...
npm ERR! git clone D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-https-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-541c96f3 D:\Users\6587\AppData\Local\Temp\npm-12540-fcf54521\git-cache-1126e2b1\7e55907cd54a2e91b96d25a660acc6a2a6453f54: error: cannot spawn sh: No such file or directory
npm ERR! git clone D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-https-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-541c96f3 D:\Users\6587\AppData\Local\Temp\npm-12540-fcf54521\git-cache-1126e2b1\7e55907cd54a2e91b96d25a660acc6a2a6453f54: fatal: unable to fork
npm ERR! git clone D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-https-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-541c96f3 D:\Users\6587\AppData\Local\Temp\npm-12540-fcf54521\git-cache-1126e2b1\7e55907cd54a2e91b96d25a660acc6a2a6453f54:
npm ERR! git clone --template=D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\_templates --mirror git@github.com:webpack/compression-webpack-plugin.git D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-e286d0b5: Cloning into bare repository 'D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-e286d0b5'...
npm ERR! git clone --template=D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\_templates --mirror git@github.com:webpack/compression-webpack-plugin.git D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-e286d0b5: error: cannot spawn ssh: No such file or directory
npm ERR! git clone --template=D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\_templates --mirror git@github.com:webpack/compression-webpack-plugin.git D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-e286d0b5: fatal: unable to fork
npm ERR! Windows_NT 10.0.14942
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "D:\\Users\\6587\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "i" "-g" "angular-cli" "--no-optional"
npm ERR! node v6.8.1
npm ERR! npm  v3.10.7
npm ERR! code 128

npm ERR! Command failed: git -c core.longpaths=true clone --template=D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\_templates --mirror git@github.com:webpack/compression-webpack-plugin.git D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-e286d0b5
npm ERR! Cloning into bare repository 'D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-e286d0b5'...
npm ERR! error: cannot spawn ssh: No such file or directory
npm ERR! fatal: unable to fork
npm ERR!
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     C:\WINDOWS\system32\npm-debug.log

[Meligy]

OK. It's certainly a git issue. If you are sure you can clone stuff from git in the same directly and from command prompt, it might be a long path issue related to long commit hash referenced by the CLI or something.

This is same source of issue in #2685 even if it's not proxy related (loading the same package via git).

This troubling dependency has been removed already in filipesilva@e986bae though. Unfortunately this is not in beta-17 yet, so to test it, you need to go into many steps, like this:

git clone https://github.com/angular/angular-cli --depth 1
cd angular-cli
npm install
npm link
cd ..
ng new sample-app --skip-npm --link-cli
cd sample-app
npm rm -D angular-cli
npm install
npm link angular-cli -D
ng serve

(The --skip-npm --link-cli and npm rm -D angular-cli exist to workaround issues when using linked NPM packages. It's another long story but this is the working solution)

If this works, and you are able to see output in http://localhost:4200/, then the problem is solved in Angular-CLI sources and you can close this issue.

Otherwise, let us know what you find instead.

P.S.
If you get issues, maybe try the --no-optional flag mentioned above with your npm install calls.

[Meligy]

Grrr... just noticed that the fix (change of dependency from github to npm registry) is not yet in this repository. It's only in one of the core contributors repository.

I guess you'll have to wait until #2709 is merged into the source to try.

Sorry for that.

[DoomerDGR8]

Ok. Awaiting.

[Meligy]

The PR has just landed. This error should go away now and I think this issue can be closed as such.

To try it out before beta-18 is released, you'll need to follow the instructions in my earlier #2725 (comment).

[filipesilva]

As @Meligy said, #2709 should fix it.

We had to use a temp git hash to get around a node-zopfli problem in windows, but using it also caused a few problems in and of itself (like this one).

In your specific case, I think this might help meanwhile: #2599 (comment)

git config --global url."https://".insteadOf git://

This'll force git to use https instead of ssh to clone repos, which seems to be the issue according to npm ERR! error: cannot spawn ssh: No such file or directory.

[DoomerDGR8]

@Meligy, after running all the command successfully in you comment (), I get this when i try to server:

E:\Web\sample-app>ng serve
You have to be inside an angular-cli project in order to use the serve command.

So, after following the comment regarding git:// -> https:// by @filipesilva, I'm wondering if I need to reverse the commands in your comment...

[Meligy]

If you want to try the git workaround with the latest beta release not master, you can:

npm uninstall -g angular-cli
npm cache clear
npm install -g angular-cli

ng new sample-app
cd sample-app
ng serve

[DoomerDGR8]

@filipesilva, here is what happens with and without the protocol fix:

C:\WINDOWS\system32>**npm uninstall -g angular-cli**
- angular-cli@1.0.0-beta.17 node_modules\angular-cli

C:\WINDOWS\system32>**npm cache clear**

Installing without protocol fix

C:\WINDOWS\system32>npm install -g angular-cli
npm ERR! git clone D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-https-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-541c96f3 D:\Users\6587\AppData\Local\Temp\npm-11768-808194f9\git-cache-d09382e9\7e55907cd54a2e91b96d25a660acc6a2a6453f54: Cloning into 'D:\Users\6587\AppData\Local\Temp\npm-11768-808194f9\git-cache-d09382e9\7e55907cd54a2e91b96d25a660acc6a2a6453f54'...
npm ERR! git clone D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-https-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-541c96f3 D:\Users\6587\AppData\Local\Temp\npm-11768-808194f9\git-cache-d09382e9\7e55907cd54a2e91b96d25a660acc6a2a6453f54: error: cannot spawn sh: No such file or directory
npm ERR! git clone D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-https-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-541c96f3 D:\Users\6587\AppData\Local\Temp\npm-11768-808194f9\git-cache-d09382e9\7e55907cd54a2e91b96d25a660acc6a2a6453f54: fatal: unable to fork
npm ERR! git clone D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-https-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-541c96f3 D:\Users\6587\AppData\Local\Temp\npm-11768-808194f9\git-cache-d09382e9\7e55907cd54a2e91b96d25a660acc6a2a6453f54:
npm ERR! git clone --template=D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\_templates --mirror git@github.com:webpack/compression-webpack-plugin.git D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-e286d0b5: Cloning into bare repository 'D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-e286d0b5'...
npm ERR! git clone --template=D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\_templates --mirror git@github.com:webpack/compression-webpack-plugin.git D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-e286d0b5: error: cannot spawn ssh: No such file or directory
npm ERR! git clone --template=D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\_templates --mirror git@github.com:webpack/compression-webpack-plugin.git D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-e286d0b5: fatal: unable to fork
npm ERR! Windows_NT 10.0.14942
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "D:\\Users\\6587\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "angular-cli"
npm ERR! node v6.8.1
npm ERR! npm  v3.10.7
npm ERR! code 128

npm ERR! Command failed: git -c core.longpaths=true clone --template=D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\_templates --mirror git@github.com:webpack/compression-webpack-plugin.git D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-e286d0b5
npm ERR! Cloning into bare repository 'D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-e286d0b5'...
npm ERR! error: cannot spawn ssh: No such file or directory
npm ERR! fatal: unable to fork
npm ERR!
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     C:\WINDOWS\system32\npm-debug.log

Running fix

C:\WINDOWS\system32>git config --global url."https://".insteadOf git://

Installing again

C:\WINDOWS\system32>npm install -g angular-cli
npm WARN addRemoteGit Error: Command failed: git -c core.longpaths=true config --get remote.origin.url
npm WARN addRemoteGit
npm WARN addRemoteGit     at ChildProcess.exithandler (child_process.js:206:12)
npm WARN addRemoteGit     at emitTwo (events.js:106:13)
npm WARN addRemoteGit     at ChildProcess.emit (events.js:191:7)
npm WARN addRemoteGit     at maybeClose (internal/child_process.js:877:16)
npm WARN addRemoteGit     at Socket.<anonymous> (internal/child_process.js:334:11)
npm WARN addRemoteGit     at emitOne (events.js:96:13)
npm WARN addRemoteGit     at Socket.emit (events.js:188:7)
npm WARN addRemoteGit     at Pipe._handle.close [as _onclose] (net.js:498:12)
npm WARN addRemoteGit  webpack/compression-webpack-plugin#7e55907cd54a2e91b96d25a660acc6a2a6453f54 resetting remote D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-ec76b2fe because of error: { Error: Command failed: git -c core.longpaths=true config --get remote.origin.url
npm WARN addRemoteGit
npm WARN addRemoteGit     at ChildProcess.exithandler (child_process.js:206:12)
npm WARN addRemoteGit     at emitTwo (events.js:106:13)
npm WARN addRemoteGit     at ChildProcess.emit (events.js:191:7)
npm WARN addRemoteGit     at maybeClose (internal/child_process.js:877:16)
npm WARN addRemoteGit     at Socket.<anonymous> (internal/child_process.js:334:11)
npm WARN addRemoteGit     at emitOne (events.js:96:13)
npm WARN addRemoteGit     at Socket.emit (events.js:188:7)
npm WARN addRemoteGit     at Pipe._handle.close [as _onclose] (net.js:498:12)
npm WARN addRemoteGit   killed: false,
npm WARN addRemoteGit   code: 1,
npm WARN addRemoteGit   signal: null,
npm WARN addRemoteGit   cmd: 'git -c core.longpaths=true config --get remote.origin.url' }
npm ERR! git clone --template=D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\_templates --mirror git://github.com/webpack/compression-webpack-plugin.git D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-ec76b2fe: Cloning into bare repository 'D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-ec76b2fe'...
npm ERR! git clone --template=D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\_templates --mirror git://github.com/webpack/compression-webpack-plugin.git D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-ec76b2fe: fatal: unable to connect to github.com:
npm ERR! git clone --template=D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\_templates --mirror git://github.com/webpack/compression-webpack-plugin.git D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-ec76b2fe: github.com[0: 192.30.253.112]: errno=Invalid argument
npm ERR! git clone D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-https-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-541c96f3 D:\Users\6587\AppData\Local\Temp\npm-17264-0003fedb\git-cache-d6c06c9f\7e55907cd54a2e91b96d25a660acc6a2a6453f54: Cloning into 'D:\Users\6587\AppData\Local\Temp\npm-17264-0003fedb\git-cache-d6c06c9f\7e55907cd54a2e91b96d25a660acc6a2a6453f54'...
npm ERR! git clone D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-https-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-541c96f3 D:\Users\6587\AppData\Local\Temp\npm-17264-0003fedb\git-cache-d6c06c9f\7e55907cd54a2e91b96d25a660acc6a2a6453f54: error: cannot spawn sh: No such file or directory
npm ERR! git clone D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-https-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-541c96f3 D:\Users\6587\AppData\Local\Temp\npm-17264-0003fedb\git-cache-d6c06c9f\7e55907cd54a2e91b96d25a660acc6a2a6453f54: fatal: unable to fork
npm ERR! git clone D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-https-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-541c96f3 D:\Users\6587\AppData\Local\Temp\npm-17264-0003fedb\git-cache-d6c06c9f\7e55907cd54a2e91b96d25a660acc6a2a6453f54:
npm WARN addRemoteGit Error: Command failed: git -c core.longpaths=true config --get remote.origin.url
npm WARN addRemoteGit
npm WARN addRemoteGit     at ChildProcess.exithandler (child_process.js:206:12)
npm WARN addRemoteGit     at emitTwo (events.js:106:13)
npm WARN addRemoteGit     at ChildProcess.emit (events.js:191:7)
npm WARN addRemoteGit     at maybeClose (internal/child_process.js:877:16)
npm WARN addRemoteGit     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
npm WARN addRemoteGit  webpack/compression-webpack-plugin#7e55907cd54a2e91b96d25a660acc6a2a6453f54 resetting remote D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-e286d0b5 because of error: { Error: Command failed: git -c core.longpaths=true config --get remote.origin.url
npm WARN addRemoteGit
npm WARN addRemoteGit     at ChildProcess.exithandler (child_process.js:206:12)
npm WARN addRemoteGit     at emitTwo (events.js:106:13)
npm WARN addRemoteGit     at ChildProcess.emit (events.js:191:7)
npm WARN addRemoteGit     at maybeClose (internal/child_process.js:877:16)
npm WARN addRemoteGit     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
npm WARN addRemoteGit   killed: false,
npm WARN addRemoteGit   code: 1,
npm WARN addRemoteGit   signal: null,
npm WARN addRemoteGit   cmd: 'git -c core.longpaths=true config --get remote.origin.url' }
npm ERR! git clone --template=D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\_templates --mirror git@github.com:webpack/compression-webpack-plugin.git D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-e286d0b5: Cloning into bare repository 'D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-e286d0b5'...
npm ERR! git clone --template=D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\_templates --mirror git@github.com:webpack/compression-webpack-plugin.git D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-e286d0b5: error: cannot spawn ssh: No such file or directory
npm ERR! git clone --template=D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\_templates --mirror git@github.com:webpack/compression-webpack-plugin.git D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-e286d0b5: fatal: unable to fork
npm ERR! Windows_NT 10.0.14942
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "D:\\Users\\6587\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g" "angular-cli"
npm ERR! node v6.8.1
npm ERR! npm  v3.10.7
npm ERR! code 128

npm ERR! Command failed: git -c core.longpaths=true clone --template=D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\_templates --mirror git@github.com:webpack/compression-webpack-plugin.git D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-e286d0b5
npm ERR! Cloning into bare repository 'D:\Users\6587\AppData\Roaming\npm-cache\_git-remotes\git-git.colasdn.top-webpack-compression-webpack-plugin-git-7e55907cd54a2e91b96d25a660acc6a2a6453f54-e286d0b5'...
npm ERR! error: cannot spawn ssh: No such file or directory
npm ERR! fatal: unable to fork
npm ERR!
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     C:\WINDOWS\system32\npm-debug.log