Meteor 1.2 needs node 10.40 or greater

[kingOtto]

A lot of Meteor people use this build pack; the recent Meteor update prompts an error on Heroku that 10.40 or greater is needed. This specifies 10.36.

[hazio]

Use the engines section of your package.json to specify the version of Node.js to use on Heroku:

{
  "name": "myapp",
  "description": "a really cool app",
  "version": "0.0.1",
  "engines": {
    "node": "0.10.40"
  }
}

[nerijunior]

@hazio where I set this package.json? The #34 is the fix!

[hazio]

@nerijunior at root directory of your meteor app.

[nerijunior]

@hazio I've tried but no effect. :(

[leonardykris]

@nerijunior I'm unsure whether you still need it, but you can fork the repository, then navigate to bin/compile_node and just change the specified node_engine in line 37 to "0.10.40"

[nerijunior]

@leonardykris Tks! I made this.

[tomodutch]

For the time being you can use my fork.
heroku create --buildpack https://github.com/tfarla/heroku-buildpack-meteor.git
I have created a PR #37 but it has not been merged yet.

[nerijunior]

@TFarla Tks but I made my own fork too! :)

[nanimokamo]

I'm still getting this Node 10.40 error... has this been fixed yet?

[yborunov]

Same problem, apparently have to make a fork.
PR #37 need to be merged.

[chrisbolin]

Has anyone had luck with engines, or are the PRs like #37 the best options?

[maxko87]

If you are going with https://github.com/maxko87/heroku-buildpack-meteor.git buildpack, make sure to use this command to set it:

heroku buildpacks:set https://github.com/maxko87/heroku-buildpack-meteor.git --app yourapp

and then push to your Heroku app.

you can't just set the buildpack on the Heroku dashboard -- it won't work.

[polkhovsky]

@maxko87 Thank you for this! I can't believe it's taking so long to fix the issue.