Would love this. Any update?

It's been nearly 4 months since the v 16 release. Will AWS Lambda support v 16 in the near future? @carlzogh @krk

v14 dose not plan to support Apple M1.
So working in v14 is little annoying.
We need v16 ASAP.
nodejs/build#2474 (comment)

Seems AWS only does LTS builds so according to the schedule https://nodejs.org/en/about/releases/ it'll be around November.

Seems AWS only does LTS builds so according to the schedule https://nodejs.org/en/about/releases/ it'll be around November.

Hopefully we'll also get proper module support also.

Is there a way to create a custom runtime to use the latest version of node? If so, can anyone point me in the right direction?

@paulcanning you have to use a docker image function, and the cold start on those is pretty bad.

Just a quick update: Node v16 just turned into LTS today 🎉

Just a quick update: Node v16 just turned into LTS today 🎉

When will we get node 16 in Lambda then?

Excited to use node v16 on Lambda with CDK nodejs-lambda-function and ESM

Looking forward to this as well! if there's anything people from the community can do to help, please let us know.

any warriors? :)

bump

If you've arrived here like I did, here's the link:
https://nodejs.org/download/release/v14.18.1/

Also here's the current runtimes for lambda for reference:
https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html

@Robert-Rendell looks like you might be new to Github. there's a great "Edit" function for replies that wont spam subscribers to this issue. Three consecutive replies is a bit silly, please don't be that person.

@Robert-Rendell looks like you might be new to Github. there's a great "Edit" function for replies that wont spam subscribers to this issue. Three consecutive replies is a bit silly, please don't be that person.

Yes I'm an escapee from bitbucket, thank you for the tip!

+1

I think they are waiting for re:Invent (NOV. 29 – DEC. 3, 2021) where they will present this as big feature :)

Github Actions as of today will start moving to Node 16 as the default for actions not specifying a version. Meanwhile AWS doesn't even provide a roadmap or any signals about this... Way to go from the market leader 🙄

For anyone stuck waiting, to avoid any issues, you should specify a node version, when setting up node in your github action .yml files.

- uses: actions/setup-node@v2
  with:
    node-version: '14'

AWS: Node.js 14 is in maintenance-mode. Users deserve to know when you're going to support the long-term support version of their runtime will be available.

@o5 do you happen to know if they mentioned anything at Re:Invent?

If node 14 support timeline is any indicator, we wont see v16 til Jan-Feb
https://aws.amazon.com/blogs/compute/node-js-14-x-runtime-now-available-in-aws-lambda/

@jessecollier hopefully, although having to wait the best part of a year to get the latest LTS version of Node is a literal joke.

If node 14 support timeline is any indicator, we wont see v16 til Jan-Feb https://aws.amazon.com/blogs/compute/node-js-14-x-runtime-now-available-in-aws-lambda/

If node 12 support timeline as an indicator then we should have had v16 support last month.

@carlzogh Any updates on this please? Probably the worst thing is leaving people in the dark about this, if we know it's in 3 months, at least we can plan accordingly in our organizations.

@jtuliani thanks for the update, I will have a play with it

Confirmed that this works on Netlify Functions. Set AWS_LAMBDA_JS_RUNTIME to nodejs16.x and it works: https://upbeat-snyder-05e8fe.netlify.app/api

It also works on Vercel with the new Build Output API

@jtuliani thanks for the update! Do you have a rough idea of the timeline before the GA?

I've tried deploying a nodejs16.x lambda runtime with cloudformation (a SAM template), and it seems to work, only in the console I have this message: "The nodejs16.x runtime is no longer supported. We recommend that you migrate your functions that use nodejs16.x to a newer runtime as soon as possible."

Hello @jtuliani 👋 That's an awesome news, congratulations 🎉 Do you have an estimate on when we could expect an official/GA release of Node 16 support?

Thanks @forty for flagging that error message, I'll get that looked at.

Regarding the exact ETA: there are a lot of moving pieces to a runtime release (console, docs, SDK, SAM, CDK, CLI, CFN, etc). There are also multiple teams involved. Plans for any one of these teams can change at short notice, for example due to a live site issue, a deployment roll-back, or surprises such as Log4J2. So, I'm sure you'll understand why I'm holding off from providing an exact schedule. However, we are getting closer :)

Thanks for a swift response @jtuliani - that's totally understandable 👍 Fingers crossed for a smooth release process 🤞 Serverless Framework users are also very eager to try the new runtime - serverless/serverless#11049 🙌

Node 16 support in Lambda is now GA: https://aws.amazon.com/about-aws/whats-new/2022/05/aws-lambda-adds-support-node-js-16/

@jtuliani wrote:

Node 16 support in Lambda is now GA: https://aws.amazon.com/about-aws/whats-new/2022/05/aws-lambda-adds-support-node-js-16/

In this announcement, the following sentence caught my attention:

Node.js 16 is the latest long-term support (LTS) release of Node.js and will be supported for security and bug fixes until April 2024.

Given that Node 16 reaches EOL in September, 2023, how is AWS planning to make security and bug fixes after that date?

See #47 for Node 18 support in Lambda