无法在Heroku上部署Hubot

时间:2013-03-13 09:42:03

标签: node.js heroku hubot

我上个月(2月13日)在Heroku上使用hubot 2.4.6部署了一个Hubot实例。

今天我想添加一个新脚本,并在部署回heroku时出现编译错误。 在更新之前,我尝试按照wiki说明部署一个全新的hubot导致完全相同的错误,这里是日志:

$ git push heroku master
Counting objects: 23, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (19/19), done.
Writing objects: 100% (23/23), 10.58 KiB, done.
Total 23 (delta 0), reused 0 (delta 0)

-----> Node.js app detected
-----> Resolving engine versions
       Using Node.js version: 0.10.0
       Using npm version: 1.1.65
-----> Fetching Node.js binaries
-----> Vendoring node into slug
-----> Installing dependencies with npm
       npm http GET https://registry.npmjs.org/optparse/1.0.3
       npm http GET https://registry.npmjs.org/hubot
       npm http GET https://registry.npmjs.org/hubot-scripts
       npm http 200 https://registry.npmjs.org/optparse/1.0.3
       npm http GET https://registry.npmjs.org/optparse/-/optparse-1.0.3.tgz
       npm http 200 https://registry.npmjs.org/hubot-scripts
       npm http GET https://registry.npmjs.org/hubot-scripts/-/hubot-scripts-2.4.2.tgz
       npm http 200 https://registry.npmjs.org/hubot
       npm http GET https://registry.npmjs.org/hubot/-/hubot-2.4.8.tgz
       npm http 200 https://registry.npmjs.org/optparse/-/optparse-1.0.3.tgz
       npm http 200 https://registry.npmjs.org/hubot-scripts/-/hubot-scripts-2.4.2.tgz
       npm http 200 https://registry.npmjs.org/hubot/-/hubot-2.4.8.tgz
       npm ERR! cb() never called!
       npm ERR! not ok code 0
 !     Failed to install --production dependencies with npm
 !     Heroku push rejected, failed to compile Node.js app

To git@heroku.com:radiant-taiga-1655.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'git@heroku.com:radiant-taiga-1655.git'

现在Hubot是2.4.8。 任何人有同样的问题或我错过了什么?

2 个答案:

答案 0 :(得分:10)

我们遇到了同样的问题。我们通过在package.json中将节点版本更改为0.8.21来修复它。

"engines": {
  "node": "= 0.8.21",
  "npm": "1.1.x"
}

答案 1 :(得分:0)

所以我在NPM 1.2.9上遇到了类似的错误,nodejs 0.9.12和npm cache clean解决了所有问题。

npm update失败后,运行npm cache clean,然后再次运行npm update

相关问题