We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This is a very nice service to the community. Thank you shelfio.
We have been waiting for updates for a while now.
This package
chrome-aws-lambda
puppeteer
puppeteer-core
chromium
The latter 2 evolve continuously. puppeteer / puppeteer-core is currently at 14.3.0, and offers Chromium 103.0.5059.0 (r1002410).
14.3.0
Chromium 103.0.5059.0 (r1002410)
chrome-aws-lambda is stuck at 10.1.0, due to build problems. PRs are not responded to.
10.1.0
@sparticuz seems to have picked up the slack.
Maybe this service should switch to that fork as dependency, and move on? Or should we consider this service defunct too?
Are there alternatives that are more up-to-date? Can we assist?
The text was updated successfully, but these errors were encountered:
Wow, thanks for pointing out the https://www.npmjs.com/package/@sparticuz/chrome-aws-lambda ! I wasn't aware of the new fork.
I'll try to update the layer with the fork.
Sorry, something went wrong.
I've just published a new layer version 27 that is based on that fork with the latest Chromium and Node 16 support!
Thanks again for pointing this out!
No branches or pull requests
This is a very nice service to the community. Thank you shelfio.
We have been waiting for updates for a while now.
This package
chrome-aws-lambda
, which itselfpuppeteer
/puppeteer-core
, which depends onchromium
The latter 2 evolve continuously.
puppeteer
/puppeteer-core
is currently at14.3.0
, and offersChromium 103.0.5059.0 (r1002410)
.chrome-aws-lambda
is stuck at10.1.0
, due to build problems. PRs are not responded to.@sparticuz seems to have picked up the slack.
Maybe this service should switch to that fork as dependency, and move on? Or should we consider this service defunct too?
Are there alternatives that are more up-to-date? Can we assist?
The text was updated successfully, but these errors were encountered: