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. API | FAQ | Contributing | Troubleshooting
0 kommentar(er)
