As the team authoring the underlying DevTools Protocol, we're excited to witness and support this flourishing ecosystem. The past few months have brought several new libraries for automating headless Chrome. Q: How does Puppeteer compare with other headless Chrome projects? Learn more about the pain points of automated browser testing and help fill those gaps.Help dogfood new DevTools Protocol features.and catch bugs!.

Grow the adoption of headless/automated browser testing.

Other frameworks could adopt Puppeteer as their foundational layer.

Provide a reference implementation for similar testing libraries.

Provide a slim, canonical library that highlights the capabilities of the DevTools Protocol.

Q: Why is the Chrome team building Puppeteer? The Chrome DevTools team maintains the library, but we'd love your help and expertise on the project! Puppeteer uses the latest versions of Chromium. In non-testing use cases, Puppeteer provides a powerful but simple API because it's only targeting one browser that enables you to rapidly develop automation scripts. However, many teams only run unit tests with a single browser (e.g. Selenium / WebDriver is a well-established cross-browser API that is useful for testing cross-browser support. Q: What is the difference between Puppeteer, Selenium / WebDriver, and PhantomJS? As the DevTools protocol and browser improve over time, Puppeteer will be updated to depend on newer versions of Chromium. Puppeteer bundles Chromium to ensure that the latest features it uses are guaranteed to be available. Look for chromium_revision in package.json. FAQ Q: Which Chromium version does Puppeteer use? This example filters out all Network domain messagesĮnv DEBUG= '* ' env DEBUG_COLORS=true node script.js 2>&1 | grep -v ''Network 'Ĭheck out contributing guide to get an overview of Puppeteer development.

# Debug output can be enabled/disabled by namespaceĮnv DEBUG= '*,-*:protocol ' node script.js # everything BUT protocol messagesĮnv DEBUG= '*:session ' node script.js # protocol session messages (protocol messages to targets)Įnv DEBUG= '*:mouse,*:keyboard ' node script.js # only Mouse and Keyboard API calls # Protocol traffic can be rather noisy.

Puppeteer headless download