aws-stepfunctions-tasks: EvaluateExpression Support for NodeJS 22

[zachaws]

Describe the feature

Add support for NodeJS 22 in the EvaluateExpression function. You can currently specify the Lambda Runtime but NodeJS 22 is not supported.

Use Case

Create the Lambda Function with NodeJS 22.

Proposed Solution

No response

Other Information

Error occurs on the synthesis.

UnscopedValidationError: The runtime nodejs22.x is currently not supported.

const replicationEvaluateExpression = new tasks.EvaluateExpression(this, 'replicationEvaluateExpression', {
      expression: '`replicationEvaluateExpression`',
      runtime: lambda.Runtime.NODEJS_22_X,
      resultPath: 'replicationEvaluateExpression'
});

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

AWS CDK Library version (aws-cdk-lib)

aws-cdk-lib@2.205.0

AWS CDK CLI version

2.1021.0

Environment details (OS name and version, etc.)

MacOS

[pahud]

Hi @zachaws,

Thank you for requesting NodeJS 22 support for the EvaluateExpression construct! This is a valid feature request.

The issue occurs because the EvaluateExpression construct maintains a hardcoded mapping of supported Node.js runtimes, and NODEJS_22_X is not currently included in this mapping.

Root Cause:
The createEvalFn function in evaluate-expression.ts has a nodeJsGuids object that maps runtime names to UUIDs for the singleton function, but it's missing an entry for NODEJS_22_X.

Solution:
We need to:

1. Add NODEJS_22_X to the runtime mapping with a new UUID
2. Ensure the underlying custom resource handler supports Node.js 22
3. Add appropriate tests

This aligns with the broader Node 22 migration tracking issue #33626.

Workaround:
For now, you can use NODEJS_20_X or omit the runtime parameter to use the default.

We'd welcome a PR contribution for this enhancement! The fix should be straightforward - adding the missing runtime mapping and ensuring test coverage. Would you be interested in contributing this feature?

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.