Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

229
Views
How do I make Heroku use node 14.x instead of 12.x?

I need Heroku to use NodeJS 14 instead of 12, how do I do that? On my computer I'm using Node 14, and I'm defining it in engines on package.json (at the root of my repo):

{
  "engines": {
    "node": "14.x"
  }
  ...
}

I have both the heorku/nodejs as well as the heroku/rails buildpack installed because this is a Ruby on Rails apps with webpack:

enter image description here

But when running my tests is Heroku, I get this error:

Error: Missing binding /app/node_modules/node-sass/vendor/linux-x64-72/binding.node
Node Sass could not find a binding for your current environment: Linux 64-bit with Node.js 12.x
Found bindings for the following environments:
  - Linux 64-bit with Unsupported runtime (88)

If I workaround the problem in the CI, I still run into trouble when deploying:

-----> Installing node-v12.16.2-linux-x64
-----> Installing yarn-v1.22.4
-----> Detecting rake tasks
-----> Preparing app for Rails asset pipeline
       Running: rake assets:precompile
       yarn install v1.22.4
       [1/5] Validating package.json...
       error imok@0.1.0: The engine "node" is incompatible with this module. Expected version "14.x". Got "12.16.2"
       error Found incompatible module.
       info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
over 4 years ago · Santiago Trujillo
1 answers
Answer question

0

In the documentation it says:

If you need a specific version of node for your Ruby application you should use multiple buildpacks to first install node then install Ruby.

which means if you deployed a Rails application, you need to remove all buildpacks and then re-add them in the correct order, first heroku/node and then heroku/rails.

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!