thunderstrike/puppeteer
thunderstrike/puppeteer
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs(troubleshooting): add aws lambda resources (#1926)

Browse Source
This commit is contained in:
Eric Bidelman 2018-01-31 15:31:32 -08:00 committed by Andrey Lushnikov
parent bae44a82d8
commit 1716a748aa
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/troubleshooting.md
View File

@ -243,3 +243,11 @@ When you click add buildpack, simply paste that url into the input, and click sa
If you need to render Chinese, Japanese, or Korean characters you may need to use a buildpack with additional font files like https://github.com/CoffeeAndCode/puppeteer-heroku-buildpack
There's also another [simple guide](https://timleland.com/headless-chrome-on-heroku/) from @timleland that includes a sample project: https://timleland.com/headless-chrome-on-heroku/.
## Running Puppeteer on AWS Lambda
AWS Lambda [limits](https://docs.aws.amazon.com/lambda/latest/dg/limits.html) deployment package sizes to ~50MB. This presents challenges for running headless Chrome (and therefore Puppeteer) on Lambda. The community has put together a few resources that work around the issues:
- https://github.com/adieuadieu/serverless-chrome/blob/master/docs/chrome.md (tracks the latest Chromium snapshots)
- https://github.com/sambaiz/puppeteer-lambda-starter-kit (uses an old version of Chromium)
- https://github.com/universalbasket/aws-lambda-chrome