![]() ![]() Running with -screenshot will produce a file named screenshot.png in the current working directory. To capture a screenshot of a page, use the -screenshot flag: chrome -headless -disable-gpu -screenshot Ĭhrome -headless -disable-gpu -screenshot -window-size = 1280,1696 Ĭhrome -headless -disable-gpu -screenshot -window-size = 412,732 The -print-to-pdf flag creates a PDF of the page: chrome -headless -disable-gpu -print-to-pdf # Taking screenshots The -dump-dom flag prints to stdout: chrome -headless -disable-gpu -dump-dom # Create a PDF There are some useful command line flags to perform common tasks. In some cases, you may not need to programmatically script Headless Chrome. If you're on the stable channel of Chrome and cannot get the Beta, I recommend using chrome-canary: alias chrome = "/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome"Īlias chrome-canary = "/Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary"Īlias chromium = "/Applications/Chromium.app/Contents/MacOS/Chromium"ĭownload Chrome Canary here. Since I'm on Mac, I created convenient aliases for each version of Chrome that I have installed. The exact location will vary from platform to platform. See /737678.Ĭhrome should point to your installation of Chrome. Puppeteer creates its own browser user profile which it cleans up on every run.Note: Right now, you'll also want to include the -disable-gpu flag if you're running on Windows. This article describes some differences for Linux users. See this article for a description of the differences between Chromium and Chrome. See Puppeteer.launch() for more information. You can also use Puppeteer with Firefox Nightly (experimental support). const puppeteer = require ( 'puppeteer' ) Ĭonst browser = await puppeteer. You create an instance 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+. Prior to v1.18.1, Puppeteer required at least Node v6.4.0. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |