// the take
A small two-part app (code editor frontend + Dockerized backend) that lets you write and run Puppeteer scripts without installing anything locally — handy for quickly testing a scraping snippet or screenshot script in a browser. Built by a former Chrome DevRel engineer, deployed to App Engine Flex.
Clean separation between the code-editor frontend and the execution backend, which runs as its own Docker container exposing both a CLI (`run_puppeteer.sh`) and an HTTP upload endpoint. The backend auto-injects the `puppeteer` require and supports top-level await, so pasted snippets run with zero boilerplate. Uses an actual installed `google-chrome-unstable` binary in the container rather than only Puppeteer's bundled Chromium, which is closer to a real browser environment.
The web service accepts arbitrary uploaded JavaScript and executes it server-side in a browser automation context — that's remote code execution as a feature, and the README mentions no auth, rate limiting, or script sandboxing beyond the Docker boundary itself. Last pushed February 2024, and Puppeteer/Chrome move fast enough that a pinned `google-chrome-unstable` image this old is likely incompatible with current Puppeteer APIs by now. Deployment is hard-wired to App Engine Flex, so there's real work to run this anywhere else. The README's own TODO admits the Puppeteer version bump in `index.html` is a manual step nobody automated.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →