Building chromium for v3.0.*

[fartbagxp]

• Adding new built binaries for puppeteer 3.0.x releases

[bestplay9384]

@fartbagxp did you add libgbm-dev dependency while compiling as authors stated in puppeteer 3.0.1 release:

The docs now include the libgbm-dev dependency that's needed for Linux builds (#5667, #5693)

Linked issues:

• docs(troubleshooting): list libgbm-dev dependency puppeteer/puppeteer#5667
• chore(docker): Add missing chromium dependency puppeteer/puppeteer#5693

I'm asking because those issues are connected especially with lambda environment :)

[bestplay9384]

As far as i tested (via lambda layer with puppeteer 3.0.4) it works fine :)

[fartbagxp]

Hmm, @bestplay9384 - didn't notice that one.
I just ran https://github.com/alixaxel/chrome-aws-lambda/blob/master/_/ansible/plays/chromium.yml using ansible on an AWS instance, should the Install Packages include libgbm1 according to puppeteer/puppeteer#5693?

What else is missing - since chromium.yml hasn't been updated since Oct 2019?

I can try to rebuild it with everything else turned on.

[fartbagxp]

It doesn't seem like libgbm1 is available, so I'll use libgbm1-dev and update the configurations before rebuilding. I noticed that the AMI in inventory.ini is running off of a 2019 version of Amazon Linux 2 but it's probably not an issue.

I'm adding the hashes of the new files, just in case anybody wanted to verify.

File	Type of Hash	Hash
chromium.br	md5	6e1eeb438f88880d41b70e8a33db29db
chromium.br	sha1	49c57d369423c27189aec03b4487fb5da75e198b
chromium.br	sha256	aaebb14231f2c80e5afd15586c1d94b6780f7ed1dcbe2b044c86592207e231d6
swiftshader.tar.br	md5	5570df5549a9faaebb3b2a3d4cbd4e84
swiftshader.tar.br	sha1	e44214200c893af265c24a2dabc738981813bcbf
swiftshader.tar.br	sha256	b42101c710e59a68d89e38b8006262f7ad0409793ae979214e5ea6ea35241d31

[alixaxel]

Thank you for this @fartbagxp! 🙇