Skip to content
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

Unable to install on npm 5.0.0 #1745

Closed
jspath opened this issue May 30, 2017 · 13 comments
Closed

Unable to install on npm 5.0.0 #1745

jspath opened this issue May 30, 2017 · 13 comments
Labels
bug something broken

Comments

@jspath
Copy link

jspath commented May 30, 2017

I updated npm to 5.0.0 and am now unable to install plotly.js.

I do not have this issue with npm 4.6.1

MBP15r-0G8WM:engagement jspath$ npm i plotly.js
npm WARN deprecated [email protected]: Project renamed to HSLuv
npm WARN deprecated [email protected]: This package has been merged into the 'mapbox-gl-style-spec' package
npm WARN deprecated [email protected]: This package has been merged with the 'mapbox-gl-style-spec' package
npm WARN deprecated [email protected]: This module has moved: please install @mapbox/point-geometry instead
npm WARN deprecated [email protected]: This module is now under the @mapbox namespace: install @mapbox/shelf-pack instead
npm WARN deprecated [email protected]: This module has moved: switch to @mapbox/unitbezier
npm WARN deprecated [email protected]: This module has moved: please install @mapbox/vector-tile instead
npm WARN deprecated [email protected]: This module is now under the @mapbox namespace: install @mapbox/whoots-js instead
npm ERR! code 128
npm ERR! Command failed: /usr/local/bin/git clone --depth=1 -q -b 22/head git://github.com/mapbox/mapbox-gl-shaders.git /Users/jspath/.npm/_cacache/tmp/git-clone-391fb4fe
npm ERR! warning: templates not found /var/folders/mt/dzsls6454wv3db_j_djv3z5c0000gp/T/pacote-git-template-tmp/git-clone-b31dd07d
npm ERR! warning: Could not find remote branch 22/head to clone.
npm ERR! fatal: Remote branch 22/head not found in upstream origin
npm ERR!

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/jspath/.npm/_logs/2017-05-30T20_23_50_760Z-debug.log

The relevant section of the log file looks like:

1182 silly resolveWithNewModule [email protected] checking installable status
1183 verbose stack Error: Command failed: /usr/local/bin/git clone --depth=1 -q -b 22/head git://github.com/mapbox/mapbox-gl-shaders.git /Users/jspath/.npm/_cacache/tmp/git-clone-391fb4fe
1183 verbose stack warning: templates not found /var/folders/mt/dzsls6454wv3db_j_djv3z5c0000gp/T/pacote-git-template-tmp/git-clone-b31dd07d
1183 verbose stack warning: Could not find remote branch 22/head to clone.
1183 verbose stack fatal: Remote branch 22/head not found in upstream origin
1183 verbose stack
1183 verbose stack     at ChildProcess.exithandler (child_process.js:206:12)
1183 verbose stack     at emitTwo (events.js:106:13)
1183 verbose stack     at ChildProcess.emit (events.js:191:7)
1183 verbose stack     at maybeClose (internal/child_process.js:877:16)
1183 verbose stack     at Socket.<anonymous> (internal/child_process.js:334:11)
1183 verbose stack     at emitOne (events.js:96:13)
1183 verbose stack     at Socket.emit (events.js:188:7)
1183 verbose stack     at Pipe._handle.close [as _onclose] (net.js:498:12)
1184 verbose cwd /Users/jspath/git/engagement
1185 verbose Darwin 16.6.0
1186 verbose argv "/Users/jspath/.nvm/versions/node/v6.9.2/bin/node" "/Users/jspath/.nvm/versions/node/v6.9.2/bin/npm" "i" "plotly.js"
1187 verbose node v6.9.2
1188 verbose npm  v5.0.0
1189 error code 128
1190 error Command failed: /usr/local/bin/git clone --depth=1 -q -b 22/head git://github.com/mapbox/mapbox-gl-shaders.git /Users/jspath/.npm/_cacache/tmp/git-clone-391fb4fe
1190 error warning: templates not found /var/folders/mt/dzsls6454wv3db_j_djv3z5c0000gp/T/pacote-git-template-tmp/git-clone-b31dd07d
1190 error warning: Could not find remote branch 22/head to clone.
1190 error fatal: Remote branch 22/head not found in upstream origin
1191 verbose exit [ 1, true ]
@etpinard
Copy link
Contributor

etpinard commented May 30, 2017

Looks like it's a problem with mapbox-gl. Not much we can do here until we resolve #1714

Merging with #1714

@etpinard
Copy link
Contributor

etpinard commented Jun 1, 2017

Reopening.

npm@5 is now npm's latest version. It ships with Node 8. Even though #1714 seems to be the one and only culprit, getting plotly.js to install properly in npm@5 deserves a ticket of its own.

Thanks @jspath for bringing this up.

@etpinard etpinard reopened this Jun 1, 2017
@etpinard etpinard added bug something broken type: maintenance labels Jun 1, 2017
@etpinard
Copy link
Contributor

etpinard commented Jun 1, 2017

Similar problems have been reported to npm: npm/npm#16830 (comment)

@etpinard
Copy link
Contributor

etpinard commented Jun 1, 2017

Something like

mapbox/mapbox-gl-js@v0.22.1...etpinard:v0.22.1-for-npm5.0.0

should do the trick.

etpinard added a commit that referenced this issue Jun 1, 2017
- so that plotly.js install properly on npm@5
- more info on:
  #1745
@etpinard
Copy link
Contributor

etpinard commented Jun 5, 2017

Update: this is still an issue with [email protected]. We'll have to go through with #1752 in the next release 1.28.0.

@aliavni
Copy link

aliavni commented Jun 5, 2017

I have the same issue here

@zkat
Copy link

zkat commented Jun 8, 2017

This should be alright as of [email protected], btw

@etpinard
Copy link
Contributor

etpinard commented Jun 8, 2017

Thanks so much @zkat 🎉

npm i plotly.js now works with [email protected]

Thank you for your hard work 👍


So, to anyone having issue installing plotly.js with npm@5, running npm i -g npm should fix that. Closing this and closing #1752

@v1r0x
Copy link

v1r0x commented Nov 17, 2017

I have the exact same error using npm 5.5.1. Is this a known problem or anything I can do to fix this?

@etpinard
Copy link
Contributor

@v1r0x would you mind giving a bit more info? I was able to npm i plotly.js successfully with npm 5.5.1.

@v1r0x
Copy link

v1r0x commented Nov 17, 2017

@etpinard Sorry, forgot to mention that it's the same as OP. But here is my output:

me@bowmore:/home/me$ LANG=C npm i plotly.js
npm WARN deprecated [email protected]: Project renamed to HSLuv
npm WARN deprecated [email protected]: This package has been merged into the 'mapbox-gl-style-spec' package
npm WARN deprecated [email protected]: This package has been merged with the 'mapbox-gl-style-spec' package
npm WARN deprecated [email protected]: This module has moved: please install @mapbox/point-geometry instead
npm WARN deprecated [email protected]: This module is now under the @mapbox namespace: install @mapbox/shelf-pack instead
npm WARN deprecated [email protected]: This module has moved: switch to @mapbox/unitbezier
npm WARN deprecated [email protected]: This module has moved: please install @mapbox/vector-tile instead
npm WARN deprecated [email protected]: This module is now under the @mapbox namespace: install @mapbox/whoots-js instead
npm ERR! code 128
npm ERR! Command failed: /usr/bin/git clone --depth=1 -q -b 22/head git://github.com/mapbox/mapbox-gl-shaders.git /home/me/.npm/_cacache/tmp/git-clone-36b47657
npm ERR! warning: templates not found /tmp/pacote-git-template-tmp/git-clone-ca33ed2f
npm ERR! warning: Could not find remote branch 22/head to clone.
npm ERR! fatal: Remote branch 22/head not found in upstream origin
npm ERR! 

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/me/.npm/_logs/2017-11-17T15_18_14_989Z-debug.log

Edit: I also tried to install it in a fresh npm inited project, but same error.

@etpinard
Copy link
Contributor

@v1r0x have you looked into #2104 (comment) ?

@v1r0x
Copy link

v1r0x commented Nov 17, 2017

@etpinard Yes, but that didn't work. I use npm in a git repo and I'm connected to github with ssh. I removed my known_hosts, but still the same error. Did I miss something from #2104 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug something broken
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants