Node v16 Released 🎉

[shellscape]

:tada: :tada: :tada: :tada: https://nodejs.medium.com/node-js-16-available-now-7f5099a97e70

PLEASE don't wait a year to implement this in a new base image!

[zbauman3]

Would love this. Any update?

[joeyaurel]

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

[say8425]

v14 dose not plan to support Apple M1. So working in v14 is little annoying. We need v16 ASAP. https://github.com/nodejs/build/issues/2474#issuecomment-839683917

[PatElder]

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

[Sparticuz]

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.

[paulcanning]

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?

[shellscape]

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

[viniciusls]

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

[paulcanning]

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

When will we get node 16 in Lambda then?

[revmischa]

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

[osdiab]

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

[ghost]

any warriors? :)

[Robert-Rendell]

bump

[Robert-Rendell]

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

[Robert-Rendell]

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

[shellscape]

@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]

@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!

[fr-an-k]

+1

[o5]

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

[theo-staizen]

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'

[jthomerson]

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.

[paul-uz]

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

[jessecollier]

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/

[paul-uz]

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

[johan13]

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.

[ParallelUniv3rse]

@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.

[OG84]

Active LTS start already 2 months ago, 2021-10-26 I can't use certain node modules which require node16 (e.g. discordjs) with the current lambda node14.

[earlybail]

wtf is the deal, this needs to have been addressed months ago

[fitzgerald1337]

if anyone on AWS team is happening to read this, Google is beating you

https://cloud.google.com/functions/docs/concepts/nodejs-runtime

[paul-uz]

Well that's embarrassing ☝️

[revmischa]

[mattghali]

sigh.. anything worth developing would be faster and easier using Tornado instead

[riderx]

I had to remove my last comment, the link to the tweet I sent was link to a person not in charge of Lamba but in AWS sorry for the false hope.

Also i saw few unkind message.

I agree it’s annoying we all wait for this, but please AWS, or any people working there do not deserve bad messages.

the only way to make things better is by trying to understand each other’s :)

[Sparticuz]

Not node 16.... But modules and top level await now supported in 14

https://github.com/aws/aws-cdk/issues/13274#issuecomment-1007262232

[ahawkins]

This is a blocker for our organization. We've migrated from Node 14 to 16 for M1 support. Our lambda projects are blocked without a Node 16 runtime.

[shellscape]

@ahawkins you'll have to use docker and upload an image for the lamba functions. fwiw this will drastically increase cold start times.

[ahawkins]

@shellscape Thanks for suggesting this workaround.

[chkp-borisko]

This is a blocker for our organization. We've migrated from Node 14 to 16 for M1 support. Our lambda projects are blocked without a Node 16 runtime.

We are in the same situation

[mwilson71]

It's really tough to understand why this is taking so long.

[shellscape]

@mwilson71 bureaucracy mostly. but then think about the number of services that Amazon offers, and how much of that probably tangentially runs off of lambda. then consider all of the internal business processes and serverless functions that Amazon must use to operate the retail business. combine all of that and it makes sense why something like this would take over 6 months. not saying it's right, or couldn't be prevented, but it does make some assemblance of sense.

[jthomerson]

@shellscape I don't see how that could be true ... AWS doesn't need to change from Node X to Node 16 where they might be using Node X. This is just about making an additional runtime environment available. Shouldn't impact their existing services. I think we're just seeing that they don't have enough resources dedicated to this, and it's not as important to them than other things, which is more disheartening.

[shellscape]

@jthomerson if I were running an org that big, I'd want to test a new version image against everything. Just because it's inconvenient to us all doesn't mean there's not a reason. If you're vendor locked, be patient. No amount of hand ringing or issue comments is going to make this move any faster.

[LukeSamkharadze]

This is such a joke

[fitzgerald1337]

@jthomerson if I were running an org that big, I'd want to test a new version image against everything. Just because it's inconvenient to us all doesn't mean there's not a reason. If you're vendor locked, be patient. No amount of hand ringing or issue comments is going to make this move any faster.

are you in fact Jeff Bezos in disguise doing damage control

[ofhouse]

If I had to guess, we have to wait until Amazon Linux 2022 becomes GA, before new runtimes for Lambda will be released.

[falnyr]

@krk @carlzogh

Sorry, if I'm pinging the wrong people, but you are the only contributors apart from @amazon-auto.

Could we get some clarity from AWS as in when to expect this? I am sure you understand we all need to make decisions when designing solutions for our customers. It would be great if we could get some information, please 🙏.

[jernejc]

An estimate would be nice at least, this is very frustrating..

[TRCSamurai]

C'mon Amazon we need a response! This is a huge blocker for some of us that use your platform

[decentralgabe]

This is a mission critical failure. Any response from the @aws-lambda-runtimes team?

[o5]

@Negan1911 @jernejc @TRCSamurai @decentralgabe

You're probably new at GitHub, so please look at my screenshot. There is a function "notification subscribe" and every stupid comment like yours sends an email notification to people who are already waiting for something new.