IFX Node 22 upgrade

All IFX integrations must run on Node 22.x by October 22, 2025.

We have performed extensive testing on our internal integrations and have found no breaking changes. While dependency compatibility is the most likely area for potential issues, all checks have passed in our environment. Because each integration is unique, we recommend validating your code to ensure compatibility.

Each integration's package.json specifies engine versions for Node and npm. Existing integrations specify Node v18.13.0 and npm v8.x. However, the Lambda's runtime setting determines the actual versions used, so this value is not required to be changed.

To avoid confusion, we recommend updating your integration's engines in package.json:

{
  ...
  "engines": {
    "node": ">=22.x",
    "npm": ">=10.x"
  }
  ...
}

Be sure to also run these versions locally when developing. Follow this guide to install Node 22 and npm 10.

The infrastructure that manages the integration bundle deployments is updated to use Node 22.x and npm 10.x. All bundles deployed after the update will use the new version. This means that, until the October deadline (se, you control when the update is made to your integrations.

You can test your integration prior to September 2 by running your integration locally with Node 22.x and npm 10.x. While the likelihood is low, there is still a possibility that integrations could encounter errors when running on Node 22, so it's best to address this proactively rather than waiting for issues to arise. Follow this guide to install and use Node.js 22 and this guide for npm.