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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Node 16.x is supported? #275

Open
outaTiME opened this issue May 21, 2022 · 4 comments
Open

Node 16.x is supported? #275

outaTiME opened this issue May 21, 2022 · 4 comments
Labels
bug Something isn't working

Comments

@outaTiME
Copy link

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
@outaTiME outaTiME added the bug Something isn't working label May 21, 2022
@Sparticuz Sparticuz mentioned this issue May 26, 2022
Open
@styfle styfle mentioned this issue Jun 7, 2022
Open
juliusfitzhugh-ccpo added a commit to dod-ccpo/atat-web-api that referenced this issue Jun 7, 2022
@juliusfitzhugh-ccpo
Implement generate-document lambda (WIP)
74c237d 
Implement lambda to generate documents (e.g., DOW) that returns
a base64 encoded string of the pdf binary. Template files are
contained in a layer and are under the /templates folder. Juice
is a third-party package to combine the html and css files.

Still troubleshooting trying to get puppeteer to run inside of
lambda using puppeteer-core and having a compressed chromium
binary added as a dependency or some alternative. The
chrome-aws-lambda package does not appear to be maintained
anymore, but someone has forked the repo and has been updating
recent versions of node (v16) and puppeteer (v14).
- https://acloudguru.com/blog/engineering/serverless-browser-automation-with-aws-lambda-and-puppeteer
- https://github.com/alixaxel/chrome-aws-lambda
- https://github.com/Sparticuz/chrome-aws-lambda
- alixaxel/chrome-aws-lambda#264
- alixaxel/chrome-aws-lambda#275

Tikcet: AT-7345
juliusfitzhugh-ccpo added a commit to dod-ccpo/atat-web-api that referenced this issue Jun 8, 2022
@juliusfitzhugh-ccpo
Implement generate-document lambda (WIP)
b9a6787 
Implement lambda to generate documents (e.g., DOW) that returns
a base64 encoded string of the pdf binary. Template files are
contained in a layer and are under the /templates folder. Juice
is a third-party package to combine the html and css files.

Still troubleshooting trying to get puppeteer to run inside of
lambda using puppeteer-core and having a compressed chromium
binary added as a dependency or some alternative. The
chrome-aws-lambda package does not appear to be maintained
anymore, but someone has forked the repo and has been updating
recent versions of node (v16) and puppeteer (v14).
- https://acloudguru.com/blog/engineering/serverless-browser-automation-with-aws-lambda-and-puppeteer
- https://github.com/alixaxel/chrome-aws-lambda
- https://github.com/Sparticuz/chrome-aws-lambda
- alixaxel/chrome-aws-lambda#264
- alixaxel/chrome-aws-lambda#275

Tikcet: AT-7345
juliusfitzhugh-ccpo added a commit to dod-ccpo/atat-web-api that referenced this issue Jun 9, 2022
@juliusfitzhugh-ccpo
Implement generate-document lambda (WIP)
aabf197 
Implement lambda to generate documents (e.g., DOW) that returns
a base64 encoded string of the pdf binary. Template files are
contained in a layer and are under the /templates folder. Juice
is a third-party package to combine the html and css files.

Still troubleshooting trying to get puppeteer to run inside of
lambda using puppeteer-core and having a compressed chromium
binary added as a dependency or some alternative. The
chrome-aws-lambda package does not appear to be maintained
anymore, but someone has forked the repo and has been updating
recent versions of node (v16) and puppeteer (v14).
- https://acloudguru.com/blog/engineering/serverless-browser-automation-with-aws-lambda-and-puppeteer
- https://github.com/alixaxel/chrome-aws-lambda
- https://github.com/Sparticuz/chrome-aws-lambda
- alixaxel/chrome-aws-lambda#264
- alixaxel/chrome-aws-lambda#275

Tikcet: AT-7345
@vladholubiev vladholubiev mentioned this issue Jun 10, 2022
Closed
@bitconym
Copy link

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

@fky2015 fky2015 mentioned this issue Jul 11, 2022
Closed
@bktan81
Copy link

bktan81 commented Aug 15, 2022 •
edited
Loading

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

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

@OiR-ptr OiR-ptr mentioned this issue Jan 3, 2023
Closed
@experionsachin
Copy link

experionsachin commented Mar 23, 2023 •
edited
Loading

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

zwliew added a commit to nusmodifications/nusmods that referenced this issue Aug 5, 2023
@zwliew
chore(export): upgrade puppeteer and chromium for Node 18 support
3a0f641 
Vercel disables Node 14 support on 15 Aug 2023, and Node 16 support on 6
Feb 2024. Let's future-proof and not worry about this for a while by
supporting Node 18.

References for migration to @sparticuz/chromium:
* alixaxel/chrome-aws-lambda#275
* https://github.com/Sparticuz/chrome-aws-lambda
* https://github.com/Sparticuz/chromium#migration-from-chrome-aws-lambda

References for upgrading puppeteer:
* https://pptr.dev/chromium-support

References for prior Node upgrades:
* #3417
* #3414
zwliew added a commit to nusmodifications/nusmods that referenced this issue Aug 5, 2023
@zwliew
chore(export): upgrade puppeteer and chromium for Node 18 support
606408c 
Vercel disables Node 14 support on 15 Aug 2023, and Node 16 support on 6
Feb 2024. Let's future-proof and not worry about this for a while by
supporting Node 18.

References for migration to @sparticuz/chromium:
* alixaxel/chrome-aws-lambda#275
* https://github.com/Sparticuz/chrome-aws-lambda
* https://github.com/Sparticuz/chromium#migration-from-chrome-aws-lambda

References for upgrading puppeteer:
* https://pptr.dev/chromium-support

References for prior Node upgrades:
* #3417
* #3414
@zwliew zwliew mentioned this issue Aug 5, 2023
Merged
zwliew added a commit to nusmodifications/nusmods that referenced this issue Aug 5, 2023
@zwliew
chore(export): upgrade puppeteer and chromium for Node 18 support
e2d7856 
Vercel disables Node 14 support on 15 Aug 2023, and Node 16 support on 6
Feb 2024. Let's future-proof and not worry about this for a while by
supporting Node 18.

References for migration to @sparticuz/chromium:
* alixaxel/chrome-aws-lambda#275
* https://github.com/Sparticuz/chrome-aws-lambda
* https://github.com/Sparticuz/chromium#migration-from-chrome-aws-lambda

References for upgrading puppeteer:
* https://pptr.dev/chromium-support

References for prior Node upgrades:
* #3417
* #3414
zwliew added a commit to nusmodifications/nusmods that referenced this issue Aug 5, 2023
@zwliew
chore(export): upgrade puppeteer and chromium for Node 18 support
0fca671 
Vercel disables Node 14 support on 15 Aug 2023, and Node 16 support on 6
Feb 2024. Let's future-proof and not worry about this for a while by
supporting Node 18.

References for migration to @sparticuz/chromium:
* alixaxel/chrome-aws-lambda#275
* https://github.com/Sparticuz/chrome-aws-lambda
* https://github.com/Sparticuz/chromium#migration-from-chrome-aws-lambda

References for upgrading puppeteer:
* https://pptr.dev/chromium-support

References for prior Node upgrades:
* #3417
* #3414
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@outaTiME @pagameba @bitconym @bktan81 @experionsachin