[BUG] Does Not Work With Node 16 or 18 about chrome-aws-lambda HOT 10 OPEN

#282

from chrome-aws-lambda.

Use @sparticuz/chromium

from chrome-aws-lambda.

@vsateesh86 Same on my side!

@talaikis I switched to @sparticuz/chromium, but after launching the browser the rest of the code is not exectuted as expected. The lambda runs into a timeout even though it is set to 60 seconds. When I used "chrome-aws-lambda" the code was working as expected. Any idea what might cause this?

EDIT
After updating the lambda node version to 20x the browser is launching as expected. The only issue I currently see is that the loading time is much longer than before. While my setup used to take like 25 seconds, it now takes around 50 seconds without major changes...

Which Lambda memory size do you recommend?

from chrome-aws-lambda.

yes getting same issue

from chrome-aws-lambda.

getting same issue

from chrome-aws-lambda.

Any update planned?

from chrome-aws-lambda.

Using this @sparticuz/chromium also getting same error. Could you please let me know any other solution for this.

from chrome-aws-lambda.

@8maxxam8 Which version of chrome-aws-lamda and puppeteer core you are using in the node20 runtime?

from chrome-aws-lambda.

@sripraveens yes I am using node20 runtime!

from chrome-aws-lambda.

@8maxxam8 Sorry I meant, which version of chrome-aws-lamda and puppeteer core you are using?

Because I was using the later version in node v14, now since v14 is not supported in lamda, In v20 this is not working for me

from chrome-aws-lambda.