Node 16.x is supported?

[outaTiME]

I am having the following error when I try to run my lambda with node 16.x, does anyone else get this?

 "Failed to launch the browser process!\n/tmp/chromium: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory\n\n\nTROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md\n"

Environment

• chrome-aws-lambda Version: ^10.1.0
• puppeteer / puppeteer-core Version: ^10.1.0
• Lambda / GCF Runtime: nodejs16.x

[bitconym]

I see the fix is implemented and a pull request is made. Any reason why is not merged yet?

[bktan81]

I've received an email from AWS that they are going to phase out the support of Nodejs12 end of 2022. I'm facing the same issue with Nodejs16 and waiting for the latest version of chrome-aws-lambda.

However, if you are looking for a temporary fix, just fake the AWS_EXECUTION_ENV, please make sure other libraries are not using the environment variable AWS_EXECUTION_ENV for anything.

exports.handler = async (_event, context, callback) => {
    //Fake the nodejs version
    process.env.AWS_EXECUTION_ENV = "AWS_Lambda_nodejs14.x";
    ...

[pagameba]

FYI https://github.com/shelfio/chrome-aws-lambda-layer has switched to https://github.com/Sparticuz/chrome-aws-lambda which supports nodejs16.x

[experionsachin]

The latest repository is https://www.npmjs.com/package/@sparticuz/chromium.
Working well with node 18 and AWS Lambda.