This example filters out all Network domain messagesĮnv DEBUG='puppeteer:*' env DEBUG_COLORS=true node script.js 2>&1 | grep -v ''Network'ĭebug your Puppeteer (node) code easily, using ndb Will be logged via the debug module under the puppeteer namespace. Now your debugger will be hit and you can debug in the test browserĮnable verbose logging - internal DevTools protocol traffic In the newly opened test browser, type F8 to resume test execution In Chrome open chrome://inspect/#devices and click inspect Run node -inspect-brk, eg node -inspect-brk node_modules/.bin/jest tests Give it a spin: Getting Started Installationĭebugger await page. Capture a timeline trace of your site to help diagnose performance issues.Run your tests directly in the latest version of Chrome using the latest JavaScript and browser features. Create an up-to-date, automated testing environment.Automate form submission, UI testing, keyboard input, etc.Crawl a SPA (Single-Page Application) and generate pre-rendered content (i.e.Generate screenshots and PDFs of pages.Most things that you can do manually in the browser can be done using Puppeteer! Here are a few examples to get you started: Puppeteer runs headless by default, but can be configured to run full (non-headless) Chrome or Chromium. Puppeteer is a Node library which provides a high-level API to control Chrome or Chromium over the DevTools Protocol. API | FAQ | Contributing | Troubleshooting

Download node puppeteer for free