How to update Node.js version in Zapier application?

Other Questions Zapier
1

I need help updating the Node.js version for my Zapier app to version 6.10.2 or higher.

I’m working with a Zapier CLI application and running into version conflicts. The documentation mentions that CLI apps should use Node.js v6.10.2, but when I check the actual runtime version using app.console.log('current node', process.version); and view it through zapier logs, it shows version 4.3.2.

I tried updating my package.json file:

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

I also modified my .travis.yml configuration:

node_js:
  - "6.10.2"

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

UPDATE

I found the solution! The key was updating the zapier-platform-core dependency to version 4.3.1 (was using 1.x before). After this change, process.version now correctly shows 6.10.3. Just changing the engines field in package.json wasn’t enough.

2

Quick heads up - after updating zapier-platform-core, don’t forget to run zapier push to deploy your changes. I once updated the dependency locally but forgot to push, so the runtime kept using the old Node.js version. If you’re on a team, make sure everyone runs npm install after pulling the updated package.json - saves you from weird local dev issues. The version mismatch between what’s in engines and what actually runs can be confusing at first.

3

Indeed, this is a common issue with Zapier CLI applications. It’s important to understand that the ‘engines’ field in package.json serves primarily as a guideline for local development environments. The real determinant for the Node.js version in your Zapier app is the zapier-platform-core dependency. I encountered a similar problem several months back and spent considerable time troubleshooting before recognizing that the core dependency was the culprit. Be sure to verify your zapier-platform-core version, as newer releases typically support the latest Node.js versions, and upgrading that dependency should resolve the issue promptly.

4

glad u figured it out! zapier-platform-core is the key here. i had a similar issue last month, couldn’t get why my engines field in package.json didn’t work. turns out, it’s the core dependency that sets the node version zapier uses for your app.