You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 15, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Jan 15, 2023. It is now read-only.
Thanks of all thank you very much for this project - it's been serving us beautifully for many years.
Similar to #329, but for node v16.x - do people have a suggestion for alternative to this project? (I'm assuming there's little chance node 16 support is added here).
@pbadenski As of this writing (Dec. 19, 2021), AWS Lambda does not support Node 16 yet so there is no point adding it to this project until it gets supported in AWS Lambda.
Reacted by Ches CC, ianthomasfry, Michael Gutierrez, chrisplassmann, ksoo5703, Michał Buczek, Serban Teodorescu, Jonathan Bird, blncoxauto and Serhii Matrunchyk
@patelvp Unfortunately not, it doesn't seem that anymore updates are being made to this repo.
In my case, I was using the serverless framework for locally testing lambda functions and we had lambdas that used AWS layers which serverless packages inside of a docker container to simulate the lambda environment. This is the repo serverless was using to get the docker images, leaving us no option to upgrade to 16. It seems that its not a huge priority for the folks at serverless to switch to the official AWS Base Images either.
We ended up ditching AWS layers and moving to private npm packages removing the need for docker while testing locally, allowing us to upgrade the lambda's runtimes to node16.
I'm not sure if your situation is similar but hopefully this can help anyone running into the same problems.
Activity
dashmug commentedon Dec 18, 2021
@pbadenski As of this writing (Dec. 19, 2021), AWS Lambda does not support Node 16 yet so there is no point adding it to this project until it gets supported in AWS Lambda.
https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html
pbadenski commentedon Dec 20, 2021
My apologies I confused this project with https://github.com/lambci/node-custom-lambda
feline-dis commentedon Aug 24, 2022
Any update on this since AWS added support for node16?
https://aws.amazon.com/about-aws/whats-new/2022/05/aws-lambda-adds-support-node-js-16/
michaelgutierrez0 commentedon Aug 24, 2022
Looks like this is becoming more urgent as Node JS 12 is being deprecated by AWS Lambda:
https://aws.amazon.com/blogs/developer/announcing-the-end-of-support-for-node-js-12-x-in-the-aws-sdk-for-javascript-v3/
patelvp commentedon Sep 27, 2022
Any updates on this?
feline-dis commentedon Sep 29, 2022
@patelvp Unfortunately not, it doesn't seem that anymore updates are being made to this repo.
In my case, I was using the serverless framework for locally testing lambda functions and we had lambdas that used AWS layers which serverless packages inside of a docker container to simulate the lambda environment. This is the repo serverless was using to get the docker images, leaving us no option to upgrade to 16. It seems that its not a huge priority for the folks at serverless to switch to the official AWS Base Images either.
We ended up ditching AWS layers and moving to private npm packages removing the need for docker while testing locally, allowing us to upgrade the lambda's runtimes to node16.
I'm not sure if your situation is similar but hopefully this can help anyone running into the same problems.