pptr.dev

Get consistent font rendering from headless Chrome screenshots across local and Docker/CI environments

Prevent memory leaks and zombie Chrome processes in a long-running headless screenshot service

Generate a Puppeteer PDF with custom header/footer templates and controlled page breaks

Abort image/stylesheet/font requests in Puppeteer by resource type, safely alongside other request interceptors

Attach Puppeteer to an already-running Chrome/Chromium instance via its WebSocket debugging endpoint instead of launching a new browser

Check Puppeteer's documented WebDriver BiDi support before relying on it, since Chrome and Firefox support differ and some CDP-parity features aren't yet implemented over BiDi

capture browser console messages and uncaught page errors in puppeteer tests

grant a specific permission and set device geolocation in puppeteer using browsercontext setpermission and page setgeolocation

enable and configure headless chrome downloads in puppeteer using cdp page.setdownloadbehavior

throttle cpu and network conditions in puppeteer using a cdpsession for performance testing

use puppeteer's locators api for auto-waiting, retrying element interactions

Send raw Chrome DevTools Protocol commands via a CDPSession in Puppeteer

Open and interact with a Chrome extension background service worker via Puppeteer CDP targets

Bridge Node.js functions into page scope in Puppeteer using page.exposeFunction()

Switch from chrome-headless-shell to the new Puppeteer headless mode and understand the difference

Create isolated Puppeteer browser contexts with browser.createBrowserContext() for parallel sessions

Generate a PDF from an HTML page using Puppeteer