Closed Praveena0989 closed 6 years ago
I'm having the same issue, any idea? no error trace 🤔
Maybe because puppeteer 0.13 needs Chromium 64.0.3264.0 (r515411)
In addition, the chrome version to use with puppeteer is declared on package.json
:
https://github.com/GoogleChrome/puppeteer/blob/master/package.json#L39
The script of this project is taking the last version available at chromium browsers, it could be different.
I proposed add a tiny CLI around installing process of puppeter: https://github.com/GoogleChrome/puppeteer/pull/1652
doing
node install.js --platform linux
but not sure if the bundle generated can be aws lambda compatible; The script of this projects is doing additional things, not sure why:
https://github.com/sambaiz/puppeteer-lambda-starter-kit/blob/master/chrome/buildChrome.sh#L23
@sambaiz can you clarify? 😄
I found this script, it's very similar but version is customizable: https://github.com/adieuadieu/serverless-chrome/blob/master/packages/lambda/builds/chromium/build/build.sh#L19
We can update our script for supporting specify the version, and then generate the version compatible with puppeteer 0.13.
You may also want to consider the api changes from .10.2 to .13, I've found that several configuration options are drastically different in .13. Changing versions might break the boilerplate code in src.
Puppeteer/Chromium guys are working on /dev/shm issue(This is the issue which makes us to use all tricks to compile chromium manually and executing it) here
actually it was removed: https://github.com/adieuadieu/serverless-chrome/issues/87
I think if we use the latest chrome version available + puppeteer 0.13 it should be works
I downloaded latest prebuilt binary from here and renamed and rezipped files to match previous file names and it is working perfectly with puppeteer 13
@Praveena0989 what build, beta? thanks!
edit: ok dev, sounds a little creepy but 👍
@Kikobeats I used beta beta-headless-chromium-64.0.3282.71-amazonlinux-2017-03.zip
I tried updating puppeteer but without success