You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I imagine the response here will just be "upgrade," but I thought I'd open an issue anyway. Because node-tar has a ~ dependency on fstream and fstream was just released with a ^ dependency on graceful-fs, node-tar no longer installs on Node 0.8.
npm ERR! Error: No compatible version found: graceful-fs@'^3.0.2'
npm ERR! Valid install targets:
npm ERR! ["1.0.0","1.0.1","1.0.2","1.1.0","1.1.1","1.1.2","1.1.3","1.1.4","1.1.5","1.1.6","1.1.7","1.1.8","1.1.9","1.1.10","1.1.11","1.1.12","1.1.13","1.1.14","1.2.0","1.2.1","1.2.2","1.2.3","2.0.0","2.0.1","2.0.2","2.0.3","3.0.0","3.0.1","3.0.2"]
npm ERR! at installTargetsError (/Users/tschaub/.nvm/v0.8.26/lib/node_modules/npm/lib/cache.js:719:10)
npm ERR! at /Users/tschaub/.nvm/v0.8.26/lib/node_modules/npm/lib/cache.js:641:10
npm ERR! at saved (/Users/tschaub/.nvm/v0.8.26/lib/node_modules/npm/node_modules/npm-registry-client/lib/get.js:138:7)
npm ERR! at Object.oncomplete (fs.js:297:15)
npm ERR! If you need help, you may report this log at:
npm ERR! <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR! <[email protected]>
Assuming people want to test on Node 0.8 (e.g. on Travis), I'm interested to hear suggestions for modules that depend on node-tar.
I think these are the alternatives:
shrinkwrap
wait for a release of 0.8 that includes a version of npm that uses a version of semver that can parse ^.
The text was updated successfully, but these errors were encountered:
I imagine the response here will just be "upgrade," but I thought I'd open an issue anyway. Because
node-tar
has a~
dependency onfstream
andfstream
was just released with a^
dependency ongraceful-fs
,node-tar
no longer installs on Node 0.8.Assuming people want to test on Node 0.8 (e.g. on Travis), I'm interested to hear suggestions for modules that depend on
node-tar
.I think these are the alternatives:
npm
that uses a version ofsemver
that can parse^
.The text was updated successfully, but these errors were encountered: