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. The problem is I haven't found any Puppeteer configuration I can use for such purpose.API | FAQ | Contributing | Troubleshooting Force my users to download Chromium at runtime (at first usage for example).Download Chromium selectively at packaging time (still on dev machine).Download all-platform Chromium when npm install (on dev machine).I should be able to do one of the following: Being current platform Linux, this very version of Chromium is then shipped regardlessly on every platform's app. The problem is: Chromium is downloaded at npm install time, and it's done selectively based on the current platform. It works nice-and-smooth except for this issue:Ĭhromium is not downloaded exception is thrown when the app is executed on a platform different than the one the app has been packaged on.īetter said, I'm developing on a Linux environment and I'm packaging my app for both Linux and Windows, Linux app works fine, Windows app doesn't. I'm building a UI-automator with Puppeteer and I'm shipping it as a Electron-packaged app.
0 kommentar(er)
