Since Puppeteer (in all configurations) controls a desktop version of Chromium/Chrome, features that are only supported by the mobile version of Chrome are not supported. You should only use this configuration if you need an official release of Chrome that supports these media formats.) (However, it is possible to force Puppeteer to use a separately-installed version Chrome instead of Chromium via the executablePath option to puppeteer.launch. This means that Puppeteer does not support licensed formats such as AAC or H.264. Puppeteer is bundled with Chromium-not Chrome-and so by default, it inherits all of Chromium's media-related limitations. (For example, video playback/screenshots is likely to fail.) There are two reasons for this: You may find that Puppeteer does not behave as expected when controlling pages that incorporate audio and video. launch ( ) Q: What features does Puppeteer not support? Give it a spin: Getting Started InstallationĬonst browser = await puppeteer. 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. 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Ĭhrome for Testing (~170MB macOS, ~282MB Linux, ~280MB Windows) that is guaranteed to
0 kommentar(er)
