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. All subsequent versions rely onNode 8.9.0+. 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 thebrowser you intend to connect to. Puppeteer-core is intended to be a lightweight version of Puppeteer for launching an existing browser installation or for connecting to a remote one. ```bashnpm i puppeteer-core or 'yarn add puppeteer-core' Since version 1.7.0 we publish the puppeteer-core package,a version of Puppeteer that doesn't download Chromium by default. To skip the download, 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. ```bashnpm i puppeteer or 'yarn add 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.

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

Download js puppeteer for free