[BUG] Support node 14.x on lambda
See original GitHub issueEnvironment
chrome-aws-lambda
Version: 5.5.0puppeteer-core
Version: 5.5.0- Node.js Version: 14.x
- Lambda Runtime:
nodejs14.x
Expected Behavior
Should work 😃
Current Behavior
Error: 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
Issue Analytics
- State:
- Created 3 years ago
- Reactions:12
- Comments:9 (1 by maintainers)
Top Results From Across the Web
AWS Lambda now supports Node.js 14
You can now author AWS Lambda functions in Node.js 14 and use its new features, such as top-level-await, enhanced diagnostics, ...
Read more >Amazon Lambda now supports Node.js 14
Amazon Lambda now supports Node.js 14 ... You can now author Amazon Lambda functions in Node.js 14 and use its new features, such...
Read more >NodeJS 14.x - Native AWS Lambda Import/Export Support
4 Answers 4 · 1. I am stuck at this point as well. · 1. There is no workaround on this, you have...
Read more >AWS Announces Node.js 14 Support for Its Function as ... - InfoQ
A developer can deploy Lambda functions using Node.js 14 by uploading the code through the Lambda console and select the Node.js 14.x runtime...
Read more >AWS Lambda Now Supports Node.js 14.x Runtime - C# Corner
Node.js 14.x runtime is a Long Term Support (LTS) version of Node.js. AWS recently shared that users can now develop AWS Lambda functions ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@justin-caldicott If you are deploying an AWS lambda instance as well I was just able to resolve this by bundling my own layer and applying that to my AWS lambda instance.
then upload
chrome_aws_lambda.zip
as a custom Lambda layer and use that as opposed to the layer maintained by @shelfio@thomaschaaf Version 6.0 published with Node 14.x support, version 7.0 will follow.