Skip to content

JupiterOne/playwright-aws-lambda

View on GitHub ↗Related repositories →

Support for running Microsoft's Playwright on AWS Lambda and Google Cloud Functions

active 2024-04-272026-02-19 (UTC)

Partial coverage16,122 / 20,159 hourly files (80%) · 2 absent upstream · 4,036 failed, retryable2024-04-242026-08-12 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
68
Pushes
3
Pull requests
2
Issues
2
Stars
41
Forks
4

Activity over time

Daily event counts in the loaded window

Line chart, 664 days from 2024-04-27 to 2026-02-19. Pushes: 3 total, peak 2 in a day. Pull requests: 2 total, peak 2 in a day. Issues: 2 total, peak 1 in a day. Comments: 15 total, peak 2 in a day. Stars: 41 total, peak 2 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

Recent activity

Latest issues, pull requests and releases

  • Pull request#81j1-prod-repo-automation[bot]2025-11-26 16:36
  • Pull request#81j1-prod-repo-automation[bot]2025-11-26 16:36
  • Issue comment#79karun0122025-08-25 10:16
    Does not work
  • Issue comment#78alexseguin2025-07-31 18:33
    Browser launch throwing error after upgrading to Node20 for AWS Lambda
  • Issue comment#79alexseguin2025-07-31 18:32
    Does not work
  • Issue comment#78rcary-tailorcare2025-07-08 16:56
    Browser launch throwing error after upgrading to Node20 for AWS Lambda
  • Issue#80felixpitterling2025-01-26 19:34
    Unable to Render WebGL Websites
  • Issue comment#78felixpitterling2025-01-26 17:31
    Browser launch throwing error after upgrading to Node20 for AWS Lambda
  • Issue comment#78ozgur35122024-12-06 23:28
    Browser launch throwing error after upgrading to Node20 for AWS Lambda
  • Issue comment#76Yangeok2024-08-24 15:22
    Content or browser has been closed error
  • Issue comment#76naruhiko-toda2024-08-23 05:02
    Content or browser has been closed error
  • Issue comment#74ryan-dutton2024-08-12 02:56
    page.goto() throwing error continuously in AWS Lambda with playwright-aws-lambda
  • Issue comment#74PrinceT0782024-07-30 04:25
    page.goto() throwing error continuously in AWS Lambda with playwright-aws-lambda
  • Issue#78PrinceT0782024-07-30 04:20
    Browser launch throwing error after upgrading to Node20 for AWS Lambda
  • Issue comment#72TheAPIguys2024-06-21 05:13
    Is there any plan to add support for Node20.x?
  • Issue comment#64Am4teur2024-05-18 17:47
    Lambda deployed with CDK - ENOENT: no such file or directory, open '/var/task/bin/chromium.br
  • Issue comment#74StevenSawtelle2024-05-02 23:00
    page.goto() throwing error continuously in AWS Lambda with playwright-aws-lambda
  • Issue comment#74PrinceT0782024-05-01 05:31
    page.goto() throwing error continuously in AWS Lambda with playwright-aws-lambda
  • Issue comment#74lugfug2024-04-28 10:44
    page.goto() throwing error continuously in AWS Lambda

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 41 stars here means stars gained during the window, not the repo's star count.