v112.0.1

@sparticuz/chromium v112.0.1, @sparticuz/chromium-min v112.0.1

The chromium-v112.0.1-layer.zip file may be uploaded directly as a layer in AWS Lambda using the following code

bucketName="chromiumUploadBucket" && \
aws s3 cp chromium-v112.0.1-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v112.0.1-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v112.0.1" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v112.0.1-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v112.0.1-pack.tar file may be uploaded to any https endpoint and the remote location may be used as the input variable in the chromium.executablePath(input) function.

Breaking

This is technically a breaking change because of the new Chromium headless version, however, no code changes are necessary

What's Changed

• Support for new Chromium 112 --headless=new flag, graphics stack enable/disable, lots of docs updates by @Sparticuz in #76

New Features

• The default headless mode is changed to "new". This is a new feature of Chromium 112
  • https://developer.chrome.com/articles/new-headless/#try-out-the-new-headless
  • https://antoinevastel.com/bot%20detection/2023/02/19/new-headless-chrome.html
• The ability to disable WebGL, which can increase performance for Non-WebGL workloads.

EDIT: NOTE! These must be called before launching chromium.

// Optional: If you'd like to use the legacy headless mode. "new" is the default.
chromium.setHeadlessMode = true;

// Optional: If you'd like to disable webgl, true is the default.
chromium.setGraphicsMode = false;

Full Changelog: v112.0.0...v112.0.1