Error building: No compatible version found: hardhat

Issue #57 resolved
Jeff Turner created an issue
$ sudo npm install -g atlasboard
npm http GET https://registry.npmjs.org/atlasboard
npm http 304 https://registry.npmjs.org/atlasboard
npm http GET https://registry.npmjs.org/express/3.0.0
npm http GET https://registry.npmjs.org/path/0.4.9
npm http GET https://registry.npmjs.org/temp/0.4.0
npm http GET https://registry.npmjs.org/underscore/1.4.2
npm http GET https://registry.npmjs.org/socket.io/0.9.13
npm http GET https://registry.npmjs.org/async/0.2.6
npm http GET https://registry.npmjs.org/cheerio/0.10.7
npm http GET https://registry.npmjs.org/ical/0.0.6
npm http GET https://registry.npmjs.org/nib/0.9.0
npm http GET https://registry.npmjs.org/stylus/0.31.0
npm http GET https://registry.npmjs.org/ejs/0.8.3
npm http GET https://registry.npmjs.org/connect-assets/2.3.3
npm http GET https://registry.npmjs.org/optimist
npm http GET https://registry.npmjs.org/hardhat
npm http GET https://registry.npmjs.org/css-parse/1.0.4
npm http GET https://registry.npmjs.org/request/2.14.0
npm http GET https://registry.npmjs.org/xtend/2.0.3
npm http GET https://registry.npmjs.org/tracer/0.5.1
npm http 304 https://registry.npmjs.org/socket.io/0.9.13
npm http GET https://registry.npmjs.org/socket.io/-/socket.io-0.9.13.tgz
npm http 304 https://registry.npmjs.org/temp/0.4.0
npm http GET https://registry.npmjs.org/temp/-/temp-0.4.0.tgz
npm http 304 https://registry.npmjs.org/express/3.0.0
npm http GET https://registry.npmjs.org/express/-/express-3.0.0.tgz
npm http 200 https://registry.npmjs.org/underscore/1.4.2
npm http GET https://registry.npmjs.org/underscore/-/underscore-1.4.2.tgz
npm http 304 https://registry.npmjs.org/nib/0.9.0
npm http GET https://registry.npmjs.org/nib/-/nib-0.9.0.tgz
npm http 200 https://registry.npmjs.org/cheerio/0.10.7
npm http GET https://registry.npmjs.org/cheerio/-/cheerio-0.10.7.tgz
npm http 200 https://registry.npmjs.org/ical/0.0.6
npm http GET https://registry.npmjs.org/ical/-/ical-0.0.6.tgz
npm http 304 https://registry.npmjs.org/stylus/0.31.0
npm http GET https://registry.npmjs.org/stylus/-/stylus-0.31.0.tgz
npm http 200 https://registry.npmjs.org/async/0.2.6
npm http GET https://registry.npmjs.org/async/-/async-0.2.6.tgz
npm http 304 https://registry.npmjs.org/ejs/0.8.3
npm http GET https://registry.npmjs.org/ejs/-/ejs-0.8.3.tgz
npm http 304 https://registry.npmjs.org/connect-assets/2.3.3
npm http GET https://registry.npmjs.org/connect-assets/-/connect-assets-2.3.3.tgz
npm http 304 https://registry.npmjs.org/hardhat
npm ERR! error installing atlasboard@0.1.1
npm http 304 https://registry.npmjs.org/path/0.4.9
npm http GET https://registry.npmjs.org/path/-/path-0.4.9.tgz

npm ERR! Error: No compatible version found: hardhat@'>=0.0.7- <0.1.0-'
npm ERR! Valid install targets:
npm ERR! ["0.0.1","0.0.2","0.0.3","0.0.4"]
npm ERR!     at installTargetsError (/usr/share/npm/lib/cache.js:488:10)
npm ERR!     at next_ (/usr/share/npm/lib/cache.js:438:17)
npm ERR!     at next (/usr/share/npm/lib/cache.js:415:44)
npm ERR!     at /usr/share/npm/lib/cache.js:408:5
npm ERR!     at saved (/usr/share/npm/lib/utils/npm-registry-client/get.js:147:7)
npm ERR!     at Object.oncomplete (/usr/lib/nodejs/graceful-fs.js:230:7)
npm ERR! You may report this log at:
npm ERR!     <http://bugs.debian.org/npm>
npm ERR! or use
npm ERR!     reportbug --attach /home/jturner/npm-debug.log npm
npm ERR! 
npm ERR! System Linux 3.5.0-17-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install" "-g" "atlasboard"
npm ERR! cwd /home/jturner
npm ERR! node -v v0.6.19
npm ERR! npm -v 1.1.4
npm ERR! message No compatible version found: hardhat@'>=0.0.7- <0.1.0-'
npm ERR! message Valid install targets:
npm ERR! message ["0.0.1","0.0.2","0.0.3","0.0.4"]
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /home/jturner/npm-debug.log
npm not ok
$ 

Comments (5)

  1. Chris Kiehl Account Deactivated

    The latest version of AtlasBoard requires node >= 0.8.0. Just install a version of node that matches those requirements. We will change AtlasBoard to complain with a better error message if it can't find a matching version of node.

  2. Jeff Turner reporter

    Thanks Chris, that might be something to include in the "Get started in 30 seconds" guide.

  3. Iván Loire

    I wonder why npm is not complaining since atlasboard package.json defines it as an engine requirement...

      "engines": {
        "node": ">=0.8"
      },
    
  4. Log in to comment