11 engineers on Hacker News describe using Puppeteer first-hand: 2 endorse it, 4 regret it, 1 are mixed.
“it's not because Puppeteer constantly hits OOM errors. So you need a high-end machine, and so it can get expensive.”
regret · production · alexdanilowicz · 2025-09-15 · source ↗ · wrong label?“We love Puppeteer and use it to power our API!”
endorse · production · huss97 · 2024-11-26 · source ↗ · wrong label?“Ended up replaced it with a puppeteer-based solution. Arguably with its own problems, but less of a black hole than wkhtmltopdf.”
mixed · production · elmo2you · 2024-01-17 · source ↗ · wrong label?“fixing all the edge cases around chrome/puppeteer/lighthouse across super slow websites was a total pain”
regret · personal · rozenmd · 2022-11-20 · source ↗ · wrong label?“We switched it out for puppeteer as it was more suited as a library for our-case.”
endorse · production · yaseer · 2021-03-03 · source ↗ · wrong label?“it was crashing a lot so we put it on a different server and called it from the main server PHP project”
regret · production · simion314 · 2020-12-05 · source ↗ · wrong label?“Puppeteer (browser automation) bugs or improper use. Certain sequence of events could deadlock it, causing timeouts relatively rarely.”
regret · production · tom-jh · 2019-05-29 · source ↗ · wrong label?“to see my puppeteer job run to do some screen scraping without having to have 15 VSCode windows open.”
neutral · production · coding123 · 2021-03-26 · source ↗ · wrong label?“we switched away from selenium to puppeteer a year ago due to reliability issues with the former.”
neutral · production · 1 yr · dbjorge · 2020-05-24 · source ↗ · wrong label?“We ended up going with React/Jest/Puppeteer”
neutral · production · howdydoo · 2019-09-27 · source ↗ · wrong label?“I'm using Puppeteer for website / transaction monitoring at checklyhq.com. People script their own checks and we run them for you”
neutral · production · tnolet · 2018-06-05 · source ↗ · wrong label?