Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node v16 Released 馃帀 #14

Closed
shellscape opened this issue Apr 20, 2021 · 158 comments
Closed

Node v16 Released 馃帀 #14

shellscape opened this issue Apr 20, 2021 · 158 comments

Comments

@shellscape
Copy link

@shellscape shellscape commented Apr 20, 2021

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

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

@shellscape shellscape changed the title Node v16 Released 馃帀 Node v16 Released 馃帀 Apr 20, 2021
@zbauman3
Copy link

@zbauman3 zbauman3 commented Jun 3, 2021

Would love this. Any update?

@nickreynke
Copy link

@nickreynke nickreynke commented Aug 13, 2021

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

@say8425
Copy link

@say8425 say8425 commented Aug 15, 2021

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

@PatElder
Copy link

@PatElder PatElder commented Aug 19, 2021

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

@Sparticuz
Copy link

@Sparticuz Sparticuz commented Sep 10, 2021

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
Copy link

@paulcanning paulcanning commented Oct 20, 2021

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
Copy link
Author

@shellscape shellscape commented Oct 20, 2021

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

@viniciusls
Copy link

@viniciusls viniciusls commented Oct 27, 2021

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

@paulcanning
Copy link

@paulcanning paulcanning commented Oct 27, 2021

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

When will we get node 16 in Lambda then?

@revmischa
Copy link

@revmischa revmischa commented Oct 27, 2021

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

@osdiab
Copy link

@osdiab osdiab commented Oct 27, 2021

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

@chengjiaapraamcos
Copy link

@chengjiaapraamcos chengjiaapraamcos commented Oct 30, 2021

any warriors? :)

@Robert-Rendell
Copy link

@Robert-Rendell Robert-Rendell commented Nov 1, 2021

bump

@Robert-Rendell
Copy link

@Robert-Rendell Robert-Rendell commented Nov 1, 2021

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

@Robert-Rendell
Copy link

@Robert-Rendell Robert-Rendell commented Nov 1, 2021

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

@shellscape
Copy link
Author

@shellscape shellscape commented Nov 1, 2021

@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
Copy link

@Robert-Rendell Robert-Rendell commented Nov 1, 2021

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

@frank-unovica
Copy link

@frank-unovica frank-unovica commented Nov 11, 2021

+1

@o5
Copy link

@o5 o5 commented Nov 26, 2021

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

@theo-staizen
Copy link

@theo-staizen theo-staizen commented Nov 29, 2021

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
Copy link

@jthomerson jthomerson commented Dec 3, 2021

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
Copy link

@paul-uz paul-uz commented Dec 6, 2021

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

@jessecollier
Copy link

@jessecollier jessecollier commented Dec 13, 2021

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
Copy link

@paul-uz paul-uz commented Dec 13, 2021

@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
Copy link

@johan13 johan13 commented Dec 13, 2021

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
Copy link

@ParallelUniv3rse ParallelUniv3rse commented Dec 16, 2021

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

@The-Code-Monkey
Copy link

@The-Code-Monkey The-Code-Monkey commented May 5, 2022

@jtuliani Do we have a more specific date yet, and also what about node 18 support as that has already been set as current and some devs might want to use it to develop and deploy ready for when 16 is put into maintenance in October.

@jtuliani
Copy link

@jtuliani jtuliani commented May 9, 2022

Update: There are multiple parts to a runtime launch. There's the managed runtime itself, the container base image, plus support in the console, SAM CLI, AWS CLI, CloudFormation, various AWS SDKs, etc. In previous releases we have coordinated all of these to land on launch day. For the Node 16 release, we're experimenting with a different approach, with the various components landing separately. A release candidate of the 'nodejs16.x' runtime identifier is already deployed (you can try it today if you deploy via the Lambda APIs directly), with the other components in progress. Once everything is complete, we'll make the GA announcement.

@fromtheexchange That's a great question regarding the alignment of RICs. This is something we currently plan to address in Node 18.

@The-Code-Monkey Let's discuss Node 18 in #47, so we keep that information in one place.

@The-Code-Monkey
Copy link

@The-Code-Monkey The-Code-Monkey commented May 9, 2022

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

@ascorbic
Copy link

@ascorbic ascorbic commented May 9, 2022

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

@JuanM04
Copy link

@JuanM04 JuanM04 commented May 9, 2022

It also works on Vercel with the new Build Output API

image

styfle added a commit to vercel/vercel that referenced this issue May 9, 2022
@forty
Copy link

@forty forty commented May 9, 2022

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

@pgrzesik
Copy link

@pgrzesik pgrzesik commented May 9, 2022

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?

@jtuliani
Copy link

@jtuliani jtuliani commented May 9, 2022

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 :)

@pgrzesik
Copy link

@pgrzesik pgrzesik commented May 9, 2022

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 馃檶

@jtuliani
Copy link

@jtuliani jtuliani commented May 13, 2022

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/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests