ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #puppeteer
When Puppeteer waits for navigation in a single‑page application (SPA) that changes URLs via history.pushState, the script can hang or timeout. This guide shows how to identify the root cause, run ordered checks, apply fixes, and know when to escalate.
Flaky staging APIs make flaky UI tests. Puppeteer's request interception lets you mock, block, or fail HTTP traffic from inside your test process — no backend required.
Use Puppeteer's request interception to abort images, fonts, and trackers, cutting scrape time and bandwidth — with a worked example, mocking via request.respond(), and the failure modes to watch for.
A practical guide to eliminating race conditions in Puppeteer headless navigation by chaining networkidle0 with explicit waitForSelector visibility checks, including retry strategies and fallback patterns for flaky pages.
Rendering your existing HTML in headless Chrome beats rebuilding layout in a PDF library — if you handle print styles, readiness, and browser memory.
A diagnostic guide for Puppeteer navigation timeouts: recognize the condition, use a cause table, run ordered checks, apply targeted fixes, and know when to escalate.
Use Puppeteer’s request interception to replace real API calls with mock responses, making end‑to‑end tests stable and fast. The post walks through a concrete example, highlights trade‑offs, and offers best‑practice tips.
A decision guide for choosing Puppeteer waiting primitives in CI. Compare waitForSelector, waitForFunction, and waitUntil for speed and stability to reduce flaky data extraction.
Learn how to use Puppeteer’s request interception to mock API calls, speed up tests, and keep UI logic isolated. A concrete example, trade‑offs, and best‑practice checklist are included.
nodejs