v119.0.2

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

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

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

• Node 20 lambda support by @Sparticuz in #187
• Updated Node 16 and 18 support by @Sparticuz in #187

Special Thanks

• @benasher44 for testing many times

Full Changelog: v119.0.0...v119.0.2

v119.0.1-next.0

@sparticuz/chromium v119.0.1-next.0, @sparticuz/chromium-min v119.0.1-next.0

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

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

The chromium-v119.0.1-next.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.

Full Changelog: v119.0.0...v119.0.1-next.0

v119.0.0

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

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

The chromium-v119.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 actions/setup-node from 3 to 4 by @dependabot in #171
• Bump @types/node from 18.18.6 to 18.18.7 by @dependabot in #170
• Add AWS SAM LayerVersion example by @davidjb in #178
• Bump @types/tar-fs from 2.0.3 to 2.0.4 by @dependabot in #181
• Bump @types/follow-redirects from 1.14.3 to 1.14.4 by @dependabot in #180
• Bump @types/node from 18.18.7 to 18.18.9 by @dependabot in #179
• add 119 by @Sparticuz in #182

New Contributors

• @davidjb made their first contribution in #178

Full Changelog: v118.0.0...v119.0.0

v118.0.0

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

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

The chromium-v118.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 actions/checkout from 3 to 4 by @dependabot in #156
• Bump ncipollo/release-action from 1.12.0 to 1.13.0 by @dependabot in #143
• Chromium 118 by @Sparticuz in #168

Full Changelog: v117.0.0...v118.0.0

v117.0.0

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

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

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

• Correct a few typos by @Jamesllllllllll in #149
• Chromium 117 by @Sparticuz in #161

New Contributors

• @Jamesllllllllll made their first contribution in #149

Full Changelog: v116.0.0...v117.0.0

v116.0.0

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

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

The chromium-v116.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 116 by @Sparticuz in #139

Full Changelog: v115.0.0...v116.0.0

v115.0.0

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

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

The chromium-v115.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 115 by @Sparticuz in #128

Full Changelog: v114.0.0...v115.0.0

v114.0.0

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

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

The chromium-v114.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 114 by @Sparticuz in #111

Bugfixes

• #105

Full Changelog: v113.0.1...v114.0.0

v113.0.1

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

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

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

• add netlify env check by @Sparticuz in #98

Full Changelog: v113.0.0...v113.0.1

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