Installing jest with old versions of npm fails due to lack of ^ (carrot) support

[bgw]

$ nvm use 0.8
Now using node v0.8.28 (npm v1.2.30)

$ npm install facebook/jest#master
npm WARN package.json eslint-plugin-fb-www@0.0.0 No repository field.
npm http GET https://registry.npmjs.org/coffee-script
npm http GET https://registry.npmjs.org/cover
npm http GET https://registry.npmjs.org/diff
npm http GET https://registry.npmjs.org/graceful-fs
npm http GET https://registry.npmjs.org/harmonize/1.4.2
npm http GET https://registry.npmjs.org/istanbul
npm http GET https://registry.npmjs.org/jasmine-only/0.1.0
npm http GET https://registry.npmjs.org/jasmine-pit
npm http GET https://registry.npmjs.org/node-haste
npm http GET https://registry.npmjs.org/optimist
npm http GET https://registry.npmjs.org/node-worker-pool
npm http GET https://registry.npmjs.org/resolve
npm http GET https://registry.npmjs.org/jsdom
npm http GET https://registry.npmjs.org/through
npm http GET https://registry.npmjs.org/lodash.template
npm http GET https://registry.npmjs.org/q
npm http 304 https://registry.npmjs.org/diff
npm WARN package.json diff@1.0.8 No readme data.
npm http 304 https://registry.npmjs.org/graceful-fs
npm http 304 https://registry.npmjs.org/coffee-script
npm ERR! Error: No compatible version found: graceful-fs@'^2.0.3'
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","3.0.3","3.0.4","3.0.5","3.0.6","3.0.7","3.0.8"]
npm ERR!     at installTargetsError (/Users/bgw/.nvm/v0.8.28/lib/node_modules/npm/lib/cache.js:719:10)
npm ERR!     at /Users/bgw/.nvm/v0.8.28/lib/node_modules/npm/lib/cache.js:641:10
npm ERR!     at saved (/Users/bgw/.nvm/v0.8.28/lib/node_modules/npm/node_modules/npm-registry-client/lib/get.js:138:7)
npm ERR!     at Object.oncomplete (fs.js:302: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!     <npm-@googlegroups.com>

npm ERR! System Darwin 14.3.0
npm ERR! command "/Users/bgw/.nvm/v0.8.28/bin/node" "/Users/bgw/.nvm/v0.8.28/bin/npm" "install" "facebook/jest#master"
npm ERR! cwd /Users/bgw/eslint-rules
npm ERR! node -v v0.8.28
npm ERR! npm -v 1.2.30
npm http 304 https://registry.npmjs.org/istanbul
npm http 304 https://registry.npmjs.org/jasmine-only/0.1.0
npm http 304 https://registry.npmjs.org/cover
npm http 304 https://registry.npmjs.org/optimist
npm WARN package.json optimist@0.6.1 No readme data.
npm http 304 https://registry.npmjs.org/node-haste
npm http 304 https://registry.npmjs.org/node-worker-pool
npm WARN package.json node-worker-pool@2.4.4 No readme data.
npm http 304 https://registry.npmjs.org/resolve
npm WARN package.json resolve@0.6.3 No readme data.
npm http 304 https://registry.npmjs.org/jasmine-pit
npm WARN package.json jasmine-pit@2.0.2 No readme data.
npm http 304 https://registry.npmjs.org/jsdom
npm http 304 https://registry.npmjs.org/through
npm http 304 https://registry.npmjs.org/lodash.template
npm WARN package.json jsdom@0.10.6 No readme data.
npm http 304 https://registry.npmjs.org/q
npm WARN package.json q@0.9.7 No readme data.
npm http 304 https://registry.npmjs.org/harmonize/1.4.2
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/bgw/eslint-rules/npm-debug.log
npm ERR! not ok code 0

This is an issue if we want to support node 0.8, as it ships with this version of npm. However, it can be worked around by running npm install npm and using node_modules/.bin/npm.

[blainekasten]

Ran into this same issue. Sounds like it's probably more of an issue that's not jest's fault though. Using old versions of npm are bound to have unexpected consequences.

[cpojer]

yap, we are not supporting old versions of node or npm any longer. Thanks for the report!

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.