While an older experiment required a patched version of Firefox, the current approach works with “stock” Firefox. Save file as example.js const puppeteer = require( 'puppeteer') Ĭonst browser = await puppeteer.launch() Īwait page.screenshot() to run your Puppeteer scripts in Firefox Nightly, without any additional custom patches. Of Browser, open pages, and then manipulate them with Puppeteer's API.Įxample - navigating to and saving a screenshot as example.png: 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
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)
