-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node LTS Update (v22) #264
Comments
Node.js v22 runtime is now available! While the documentation updates are not yet released, we can already use the v22 runtime in Lambda. |
App Runner is not Lambda though.... This is specifically about node 22 runtimes in that platform |
@davecarlson Apologies for the confusion! You're absolutely right—this is specifically about the Node.js v22 runtime in Lambda, not App Runner. Thanks for pointing that out! |
Then why are you commenting here? It is unrelate and not helpful to the issue at hand. |
Community Note
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about your request
What do you want us to build?
We are currently stuck on Node 18, despite at least node20 being available inside the al2023 base image...
Node 22 is now the current Long Term Stable recommended version, could us users please have some form of update on when this (or at least 20!) will be supported. Infrastructure tickets need to be scheduled, and we've already had to pause releasing one feature out as it requires some of the Node 20 (now released 18 months ago...) APIs
All us users want is some level of communication so we can plan!
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Anything else we should know?
Attachments
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)
The text was updated successfully, but these errors were encountered: