How to update Node.js version in Zapier applications?

[OwenNebula55]

I need help updating the Node.js version for my Zapier application to version 6.10.2 or newer.

I’m working with a Zapier CLI app and I’m getting confused by different documentation. One place says CLI apps use Node.js v6.10.2, but another section mentions the environment runs vanilla Node.js v4.3.2.

When I check the actual version by adding console.log('current node version:', process.version); in my app code and view it with zapier logs, it shows version 4.3.2.

I tried updating my package.json file from this:

"engines": {
  "node": ">=4.3.2",
  "npm": ">=2.0.0"
}

To this configuration:

"engines": {
  "node": "6.10.2",
  "npm": ">=2.0.0"
}

I also modified my travis.yml settings:

node_js:
  - "6.10.2"

But the runtime version hasn’t changed. What am I missing?

UPDATE - FOUND THE FIX

The solution was updating the zapier-platform-core dependency to version 4.3.1 (I was using 1.x before). After this change, checking process.version now returns 6.10.3 as expected.

[ZoeStar42]

Zapier completely ignores the engines field in package.json - that’s why your first attempt failed. Instead, Zapier picks the Node.js version based on your zapier-platform-core dependency version. Each platform core version maps to a specific Node.js runtime on their servers. When you upgraded from 1.x to 4.3.1, you jumped from the old v4.3.2 runtime to the newer v6.10.x environment. It’s documented somewhere, but easy to miss since most devs expect engines to actually control the runtime version.

[Liam_25Meditation]

so happy you figured it out! I ran into the same thing b4 too, super frustrating lol. you’re spot on about the zapier-platform-core version being key, not just that engines part in package.json. def check the core dependency first if any1 else has this issue.

[Noah_Fire]

Yeah, this catches tons of developers coming from other platforms. Zapier ties your Node.js version to your dependency version, which makes sense for them (they need compatibility between platform features and Node runtime) but it’s definitely not obvious if you’re used to normal deployment setups. Quick heads up - if you’re planning to upgrade later, each major zapier-platform-core version usually means a newer Node.js version, so check their changelog before updating. The platform core is both your SDK and runtime selector, which is why just setting engines in package.json doesn’t work like it would on Heroku.