無法在Heroku上部署Hubot

Question

我在上個月（2月13日）使用hubot 2.4.6在Heroku上部署了一個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。 任何人有同樣的問題或我錯過了什么？

Answer 1

我們遇到了同樣的問題。 我們通過在package.json中將節點版本更改為0.8.21來修復它。

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

Answer 2

所以我在NPM 1.2.9上遇到過類似的錯誤，nodejs 0.9.12和npm cache clean修復了一切。

在npm update失敗后，運行npm cache clean ，然后再次運行npm update 。