Ndb jest or ndb mocha (or npx ndb jest / npx ndb mocha)ĭebug your test inside chromium like a boss! Npm install -g ndb (or even better, use npx!)Īdd a debugger to your Puppeteer (node) codeĪdd ndb (or npx ndb) before your test command. 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.
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. puppeteerrc.cjs (or | FAQ | Contributing | Troubleshooting Puppeteer uses several defaults that can be customized through configurationįor example, to change the default cache directory Puppeteer uses to installīrowsers, you can add a.
Include $HOME/.cache into the project's deployment.įor a version of Puppeteer without the browser installation, see Your project folder (see an example below) because not all hosting providers Heroku, you might need to reconfigure the location of the cache to be within
If you deploy a project using Puppeteer to a hosting provider, such as Render or The browser is downloaded to the $HOME/.cache/puppeteer folderīy default (starting with Puppeteer v19.0.0). When you install Puppeteer, it automatically downloads a recent version ofĬhromium (~170MB macOS, ~282MB Linux, ~280MB Windows) that is guaranteed to # or `yarn add puppeteer` # or `pnpm i puppeteer`
0 kommentar(er)
