Ngx-admin: Can't install amcharts and ammap

[Gelio]

• I'm submitting a ...
  [x] bug report
  [ ] feature request
  [ ] question about the decisions made in the repository
• Do you want to request a _feature_ or report a _bug_?
  Report a bug
• What is the current behavior?
  When running npm install on Windows 10 (using _git for windows_) I am prompted with the following error:

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:493:12)
npm WARN addRemoteGit  amcharts/ammap3 resetting remote C:\Users\voren\AppData\Roaming\npm-cache\_git-remotes\git-github-com-amcharts-ammap3-git-5b4c9c11 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:493: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' }

• If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via
  https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).
  Simply run npm install on Windows 10
• What is the expected behavior?
  Successful installation.
• What is the motivation / use case for changing the behavior?
• Please tell us about your environment:
• Angular version: 2.0.0
• Browser: all
• npm: 3.10.7
• node: v6.5.0
• using Cmder on Windows 10
• Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)
  I did some research and it turns out, that it's the problem with using SSH when installing a package from GitHub via npm.
  I changed _package.json_ to use full git urls:

    "amcharts3": "[email protected]:amcharts/amcharts3.git",
    "ammap3": "[email protected]:amcharts/ammap3.git",

And it works for me now. I can submit a PR if this change doesn't cause problems on Linux/Mac. It certainly does for me.

[nnixaa]

Hey @Gelio, we looked into quickly and unfortunately this isn't working on windows.
Also, current way of installing the package is the recommended by amchart supporters.

Not sure how to proceed with it, let's keep it open for now and see if anyone has same/similar issue.

[Brqqq]

I have the same issue, though I believe for me it has something to do with corporate proxy and self signed SSL certificates. Using npm version 3.10.8, node version 6.8.0 with git bash on windows 7.

I think maybe my issue is a bit different. The provided workaround doesn't work for me. I can add the links to full github https urls in packages.json, but I'll get an error about self signed certificates (because of the proxy) when it tries to do 'git clone'. Even if I disable strict ssl checking in git, it will still give me that. However, cloning the repo manually will work fine (even with the exact command that npm executes), as npm seemingly ignores my git configurations when it performs git commands.

Anyways just documenting my findings here if it's relevant.

[AyerCai]

The same issue here.
npm: 3.10.8
node: v6.9.1
Windows 10

The others were successful except for
"amcharts3": "github:amcharts/amcharts3",
"ammap3": "github:amcharts/ammap3",

[logan2013]

@AyerCai I think the reason is that github is too slow in China. maybe you can use proxy or clone these two repos to your machine

[nik2906]

I was having the same problem. This is what I did which ultimately solved the issue:

1. open package.json file
2. Under dependencies, remove these two values -
   "ammap3": "github:amcharts/ammap3",
   "amcharts3": "github:amcharts/amcharts3",

1. Then run npm install. It will work just fine and create a folder by the name of node_modules
   Inside this folder, clone the following repositories as-

git clone https://github.com/amcharts/ammap3.git
git clone https://github.com/amcharts/amcharts3.git

1. run npm start and see the magic.

[ssatguru]

I bet this has something to do with corporate proxy. Works at home not office.
@nik2906 solution worked !!