Skip to main content

IFX Node 22 upgrade

AWS is deprecating Node.js v18, so all IFX integration Lambdas must be upgraded to Node.js v22.

Read more in the AWS documentation and explore what's new in Node.js 22.

What this means for you

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.

Note

If you have bundles deployed with v18 that you want to preserve, download them before redeploying. Any redeploy after the cutover will automatically use Node 22.

Timeline and details

Date

Action

September 2, 2025

Sandbox and Production

The infrastructure that manages the integration bundle deployments is updated to use Node 22.x and npm 10.x.

You can test before this date by running your integration locally using these versions. 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.

Any bundles deployed after the update will use the new version. This means that, until the October deadline (see below), you control when the update is made to your integrations.

When you are confident your bundle continues to run under Node 22, redeploy your integration in Sandbox and test it. When testing passes, you can continue to Production.

If you encounter any issues, you can roll back by promoting the last bundle deployed with 18.x. Include v22 in your newer bundle's name to ensure you know which bundles use which version.

Note

This method is an option only until October 21, 2025.

October 21, 2025

Deadline for customer-driven upgrade

All remaining integration Lambdas with deployed bundles running on Node 18.x are automatically updated to Node 22.x in both Sandbox and Production.

There is no downtime for integrations during this upgrade.

In this section: