๐๏ธ Configuration
By default, Puppeteer downloads and uses a specific version of Chrome so its
๐๏ธ Debugging
Debugging with Puppeteer can be an arduous task. There is no single method for
๐๏ธ Request Interception
Once request interception is enabled, every request will stall unless it's
๐๏ธ Headless mode
By default Puppeteer launches the browser in
๐๏ธ Screenshots
For capturing screenshots use Page.screenshot().
๐๏ธ PDF generation
For printing PDFs use Page.pdf().
๐๏ธ Chrome Extensions
Puppeteer can be used for testing Chrome Extensions.
๐๏ธ Cookies
Puppeteer allows modifying cookies for a page ahead of time by using Page.setCookie().
๐๏ธ Files
Currently, Puppeteer does not offer a way to handle file downloads in a programmatic way.
๐๏ธ Running Puppeteer in the browser
Puppeteer is a powerful tool for automating browsers, but did you know it can also run within a browser itself? This enables you to leverage Puppeteer's capabilities for tasks that don't require Node.js specific features.
๐๏ธ Running Puppeteer in Chrome extensions
Chrome extensions environment is significantly different from the usual Node.JS environment, therefore, the support for running Puppeteer in chrome.debugger