v113.0.0

@sparticuz/chromium v113.0.0, @sparticuz/chromium-min v113.0.0

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

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

The chromium-v113.0.0-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

• Node 14 support has been dropped by Puppeteer, This package also drops Node 14 support.

What's Changed

• Bump @types/node from 18.15.7 to 18.15.11 by @dependabot in #84
• Bump typescript from 5.0.2 to 5.0.3 by @dependabot in #83
• Bump typescript from 5.0.3 to 5.0.4 by @dependabot in #86
• Update to chromium 113 by @Sparticuz in #97

Full Changelog: v112.0.2...v113.0.0

v112.0.2

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

The chromium-v112.0.2-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.2-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v112.0.2-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v112.0.2" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v112.0.2-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v112.0.2-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.

What's Changed

• Re-add --single-process to avoid chromium error by @Sparticuz in #81

Full Changelog: v112.0.1...v112.0.2

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

v112.0.0

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

The chromium-v112.0.0-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.0-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v112.0.0-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v112.0.0" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v112.0.0-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v112.0.0-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.

What's Changed

• Bump typescript from 4.9.5 to 5.0.2 by @dependabot in #72
• Bump @types/node from 18.14.0 to 18.15.3 by @dependabot in #71
• Chromium 112 by @Sparticuz in #74

Full Changelog: v111.0.0...v112.0.0

v111.0.0

@sparticuz/chromium v111.0.0, @sparticuz/chromium-min v111.0.0

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

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

The chromium-v111.0.0-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.

What's Changed

• Add chromium-min example by @Sparticuz in #59
• Add Chromium 111 by @Sparticuz in #61
• Bump @types/node from 18.11.18 to 18.14.0 by @dependabot in #62
• Bump typescript from 4.9.4 to 4.9.5 by @dependabot in #47

Full Changelog: v110.0.1...v111.0.0

v110.0.1

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

The chromium-v110.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-v110.0.1-layer.zip "s3://${bucketName}/chromiumLayers/chromium-v110.0.1-layer.zip" && \
aws lambda publish-layer-version --layer-name chromium --description "Chromium v110.0.1" --content "S3Bucket=${bucketName},S3Key=chromiumLayers/chromium-v110.0.1-layer.zip" --compatible-runtimes nodejs --compatible-architectures x86_64

The chromium-v110.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.

What's Changed

• Build the typescript when building the layer manually by @Sparticuz in #52
• Add examples by @Sparticuz in #54
• Add follow-redirects by @Sparticuz in #57

Full Changelog: v110.0.0...v110.0.1

v110.0.0

@sparticuz/chromium v110.0.0, @sparticuz/chromium-min v110.0.0

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

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

The chromium-v110.0.0-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.

What's Changed

• Chromium 110 by @Sparticuz in #44

Full Changelog: v109.0.6...v110.0.0

v109.0.6

@sparticuz/chromium v109.0.6, @sparticuz/chromium-min v109.0.6

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

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

The chromium-v109.0.6-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.

What's Changed

• Cleanup by @Sparticuz in #30
• feat: load chromium binary remote by @aqaurius6666 in #32
• Github actions by @Sparticuz in #36
• Bump actions/setup-python from 3 to 4 by @dependabot in #37

Full Changelog: v109.0.1...v109.0.6