Error with npm install on project

After getting sources from npm install britecharts d3-selection command, and trying to install dependencies on britecharts I get the following error:

$ npm install
npm WARN deprecated babel-istanbul-loader@0.1.0: Package is deprecated, use https://github.com/deepsweet/istanbul-instrumenter-loader
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  git://github.com/beevelop/grunt-release.git resetting remote C:\Users\Ludovic\AppData\Roaming\npm-cache\_git-remotes\git-github-com-beevelop-grunt-release-git-f3dd0c51 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 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  requirejs/text resetting remote C:\Users\Ludovic\AppData\Roaming\npm-cache\_git-remotes\git-github-com-requirejs-text-git-37804fea 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' }

I expect to have dependencies installed and to build the library into dist/ folder using npm run prodcommand line.

Environment

• Britecharts: latest using npm install britecharts d3-selection
• Node version: 6.9.1
• NPM version: 3.10.8
• Operating System and version (desktop or mobile): Windows 10

[Golodhros]

Hi @ludope ,

Oh yeah, we have a delay between our bower/git releases and our NPM releases. Right now, NPM is a bit out of date compared to bower/git. This is because in our company we need help from OPS in order to release a new version. We will do it pretty soon, but I can’t give you times…

In the meanwhile, if you need the legend working fine, I would either use bower, or directly use a git link in your package.json. That would give you the most updated version, with the Legend working fine.

Also you could clone the repo and run install and prod, so you will also have that legend with the latests changes.

[ludope]

Hi @Golodhros, I cloned the repo in a Debian machine and it compiles almost successfully.

I get some UglifyJs warnings on the npm run prod but the compilation is done. I can see that d3 is not required anymore in legend.min.js as it should be. The issue should comes from my Windows environment.

Thank you for you time!