メロアップデートはヒロクのノードバージョンをアップデートしていません

Question

最近メテオバージョンを1.6にアップデートしました。しかし、私はそれをヒロクに押し込んだとき、それは墜落した。デバッグしようとしましたが、使用されているノードのバージョンが4.7で、8.8にアップグレードされているはずです。

新しいherokuアプリを作成して同じコードをプッシュし、バージョン8.8.1のノードをインストールしてアプリが正常に動作しました。

私はmeteor-build-packを英雄の配備に使用しています。私は冗長オプションでアプリケーションを展開しようと、次の出力を得た：

Delta compression using up to 4 threads. 
Compressing objects: 100% (4/4), done. 
Writing objects: 100% (4/4), 4.04 KiB | 0 bytes/s, done. 
Total 4 (delta 3), reused 0 (delta 0) 
remote: Compressing source files... done. 
remote: Building source: 
remote: 
remote: -----> Node.js app detected 
remote: + dirname -- /app/tmp/buildpacks/e8ef66c97ff87490036b0bdac9cc69618b4e878ee154e54a4c440c97fedc6dea65411bdc09dedcae43db0b412deddd38898a0dbc60489b7d8bb75b29bc0e1628/bin/compile 
remote: + cd -P -- /app/tmp/buildpacks/e8ef66c97ff87490036b0bdac9cc69618b4e878ee154e54a4c440c97fedc6dea65411bdc09dedcae43db0b412deddd38898a0dbc60489b7d8bb75b29bc0e1628/bin 
remote: + cd .. 
remote: + pwd -P 
remote: + BUILDPACK_DIR=/app/tmp/buildpacks/e8ef66c97ff87490036b0bdac9cc69618b4e878ee154e54a4c440c97fedc6dea65411bdc09dedcae43db0b412deddd38898a0dbc60489b7d8bb75b29bc0e1628 
remote: + APP_CHECKOUT_DIR=/tmp/build_323a962de4ff4f5ff909303519587f02 
remote: + APP_SOURCE_DIR=/tmp/build_323a962de4ff4f5ff909303519587f02 
remote: + [ -n ] 
remote: + [ ! -d /tmp/build_323a962de4ff4f5ff909303519587f02/.meteor ] 
remote: + [ ! -d /tmp/build_323a962de4ff4f5ff909303519587f02/.meteor ] 
remote: + mktemp -d /app/tmp/buildpacks/e8ef66c97ff87490036b0bdac9cc69618b4e878ee154e54a4c440c97fedc6dea65411bdc09dedcae43db0b412deddd38898a0dbc60489b7d8bb75b29bc0e1628/meteor-XXXX 
remote: + METEOR_DIR=/app/tmp/buildpacks/e8ef66c97ff87490036b0bdac9cc69618b4e878ee154e54a4c440c97fedc6dea65411bdc09dedcae43db0b412deddd38898a0dbc60489b7d8bb75b29bc0e1628/meteor-UUbt 
remote: + COMPILE_DIR_SUFFIX=.meteor/heroku_build 
remote: + COMPILE_DIR=/tmp/build_323a962de4ff4f5ff909303519587f02/.meteor/heroku_build 
remote: + [ -z 1 ] 
remote: + mkdir -p /tmp/build_323a962de4ff4f5ff909303519587f02 /app/tmp/buildpacks/e8ef66c97ff87490036b0bdac9cc69618b4e878ee154e54a4c440c97fedc6dea65411bdc09dedcae43db0b412deddd38898a0dbc60489b7d8bb75b29bc0e1628/meteor-UUbt /tmp/build_323a962de4ff4f5ff909303519587f02/.meteor/heroku_build 
remote: + PATH=/app/tmp/buildpacks/e8ef66c97ff87490036b0bdac9cc69618b4e878ee154e54a4c440c97fedc6dea65411bdc09dedcae43db0b412deddd38898a0dbc60489b7d8bb75b29bc0e1628/meteor-UUbt/.meteor:/tmp/build_323a962de4ff4f5ff909303519587f02/.meteor/heroku_build/bin:/usr/local/bin:/usr/bin:/bin:/tmp/codon/vendor/bin 
remote: + [ -z https://peopablility-dev.herokuapp.com/ ] 
remote: + [ -z https://peopablility-dev.herokuapp.com/ ] 
remote: + echo -----> Installing node 
remote: -----> Installing node 
remote: + curl -sS --get https://semver.io/node/resolve/4.4.x 
remote: + NODE_VERSION=4.4.7 
remote: + NODE_URL=http://s3pository.heroku.com/node/v4.4.7/node-v4.4.7-linux-x64.tar.gz 
remote: + curl -sS http://s3pository.heroku.com/node/v4.4.7/node-v4.4.7-linux-x64.tar.gz -o - 
remote: + tar -zxf - -C /tmp/build_323a962de4ff4f5ff909303519587f02/.meteor/heroku_build --strip 1 
remote: + export npm_config_prefix=/tmp/build_323a962de4ff4f5ff909303519587f02/.meteor/heroku_build 
remote: + export CPATH=/tmp/build_323a962de4ff4f5ff909303519587f02/.meteor/heroku_build/include 
remote: + export CPPPATH=/tmp/build_323a962de4ff4f5ff909303519587f02/.meteor/heroku_build/include 

次のように（期待通りに働いていた）新しいアプリに押し込みながら、私が得た出力は次のようになります。

Counting objects: 4, done. 
Delta compression using up to 4 threads. 
Compressing objects: 100% (4/4), done. 
Writing objects: 100% (4/4), 4.04 KiB | 0 bytes/s, done. 
Total 4 (delta 3), reused 0 (delta 0) 
remote: Compressing source files... done. 
remote: Building source: 
remote: 
remote: -----> Node.js app detected 
remote: -----> Installing meteor 
remote: Downloading Meteor distribution 
remote: 
remote: Meteor 1.6 has been installed in your home directory (~/.meteor). 
remote: 
remote: Now you need to do one of the following: 
remote: 
remote: (1) Add "$HOME/.meteor" to your path, or 
remote: (2) Run this command as root: 
remote:   cp "/app/tmp/cache/meteor/.meteor/packages/meteor-tool/1.6.0/mt-os.linux.x86_64/scripts/admin/launch-meteor" /usr/bin/meteor 
remote: 
remote: Then to get started, take a look at 'meteor --help' or see the docs at 
remote: docs.meteor.com. 
remote: -----> Target Meteor version: Meteor 1.6 
remote: -----> Checking if this meteor version supports --server-only 
remote: -----> Using node: v8.8.1 
remote: -----> and npm: 5.4.2 
remote: 
remote: > bcrypt@1.0.3 install /tmp/build_21ef7e1fdbfb1b38dabd9b1b9890a874/node_modules/bcrypt 
remote: > node-pre-gyp install --fallback-to-build 
remote: 
remote: [bcrypt] Success: "/tmp/build_21ef7e1fdbfb1b38dabd9b1b9890a874/node_modules/bcrypt/lib/binding/bcrypt_lib.node" is installed via remote 
remote: added 218 packages in 9.596s 
remote: -----> Building Meteor app with ROOT_URL: https://peopability-local.herokuapp.com 
remote: Warning: missing space before text for line 3 of jade file "imports/ui/components/capabilityAssessmentQuestions/capabilityAssessmentQuestion.tpl.jade" 
remote: Warning: missing space before text for line 17 of jade file "imports/ui/components/capabilityAssessmentQuestions/capabilityAssessmentQuestionDetail.tpl.jade" 
remote: Warning: missing space before text for line 2 of jade file "imports/ui/components/organisationUser/organisationUserAskedQuestion.tpl.jade" 
remote: -----> Moving built slug to /tmp/build_21ef7e1fdbfb1b38dabd9b1b9890a874/.meteor/heroku_build/app 
remote: -----> Installing npm production dependencies on built slug 
remote: 
remote: > fibers@2.0.0 install /tmp/build_21ef7e1fdbfb1b38dabd9b1b9890a874/.meteor/heroku_build/app/programs/server/node_modules/fibers 
remote: > node build.js || nodejs build.js 

どれでも助けていただければ幸いです。前もって感謝します！

Answer 1

次の解決策が私に役立ちました。

buildpackを削除してもう一度作成しました。

heroku buildpacks:clear --app appName 
heroku buildpacks:set https://github.com/AdmitHub/meteor-buildpack-horse.git --app appName 

次に、私が望むバージョンにherokuの設定変数としてNODE_VERSIONを設定しました。

heroku config:set NODE_VERSION=8.8.1 --app appName 

この後、展開は正常に機能します。