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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does not work #79

Open
blu-towers opened this issue Nov 26, 2024 · 2 comments
Open

Does not work #79

blu-towers opened this issue Nov 26, 2024 · 2 comments

Comments

@blu-towers
Copy link

I have tried multiple ways for the last few days. Works perfectly fine locally but does not want to work on lambda, i have even tried Puppeteer with all the plugins i could find nothing works if anyone has something actually working in lambda let me know.

I think for now the best bet is full blown Docker and i have a mac silicone chip, yay
#74

@F3lixP4lm
Copy link

Hello, I got it working today.
It only worked for me with the following setup with NodeJS.

  • The dependencies in the package.json with these versions

“dependencies": {
“playwright-aws-lambda": ‘^0.10.0’,
“playwright-core": ”^1.49.1”
}

  • NodeJs version 18.
  • In AWS Lambda (x86_64) manually lock the Node version to this version:
    arn:aws:lambda:us-east-1::runtime:0cdcfbdefbc5e7d3343f73c2e2dd3cba17d61dea0686b404502a0c9ce83931b9

This also worked in Ohio for me...
arn:aws:lambda:us-east-2::runtime:0cdcfbdefbc5e7d3343f73c2e2dd3cba17d61dea0686b404502a0c9ce83931b9

@Sribalajivelan
Copy link

Thanks @F3lixP4lm, I'm faced issue like

[pid=13][err] /tmp/chromium: error while loading shared libraries: libnspr4.so: cannot open shared object file: No such file or directory

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

3 participants