Lambda preset compatibility with Node.js 24 handler requirements
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 11.2k
- Forks
- 899
- Avg merge
- 2d 24m
- Merged PRs (30d)
- 40
Description
Describe the feature
Problem
While currently running the project on AWS Lambda with Node.js 22 (which still supports callback-based handlers), I see the following log warning:
AWS Lambda has removed support for callback-based function handlers starting with Node.js 24. You will need to modify this function to use a supported handler signature when upgrading to Node.js 24 or later. To disable this warning, set the AWS_LAMBDA_NODEJS_DISABLE_CALLBACK_WARNING environment variable. For more information see https://docs.aws.amazon.com/lambda/latest/dg/nodejs-handler.html.
Question / Request
Is there a plan to update the AWS Lambda preset for future compatibility with Node.js 24+, where callback-based handlers will no longer be supported? If there are migration steps or timelines already planned, please provide details. Otherwise, it would be helpful to clarify if such a migration will occur before Node.js 24 becomes the default on AWS Lambda.
Additional information
- Would you be willing to help implement this feature?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the AWS Lambda preset and its callback-based handler implementation, then review the AWS Lambda Node.js handler requirements linked in the issue for Node.js 24. Done should mean the preset is compatible with Node.js 24+ without callback-based handler warnings, with migration guidance or a documented timeline if implementation is not yet planned.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, node.js, typescript
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100