![]() Puppeteer will be familiar to people using other browser testing frameworks. All examples below use async/await which is only supported in Node v7.6.0 or greater. Starting from v3.0.0 Puppeteer starts to rely on Node 10.18.1+. Note: Prior to v1.18.1, Puppeteer required at least Node v6.4.0. Puppeteer follows the latest maintenance LTS version of Node. Be sure that the version of puppeteer-core you install is compatible with the Puppeteer-core is intended to be a lightweight version of Puppeteer for launching an existing browser installation or for connecting to a remote one. Since version 1.7.0 we publish the puppeteer-core package,Ī version of Puppeteer that doesn't download any browser by default. To skip the download, or to download a different browser, see Environment variables. Note: When you install Puppeteer, it downloads a recent version of Chromium (~170MB Mac, ~282MB Linux, ~280MB Win) that is guaranteed to work with the API. To use Puppeteer in your project, run: npm i puppeteer Give it a spin: Getting Started Installation 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |