Note: Of course, chrome-launcher is only to demonstrate an instance creation. All we’ve to do is supplying the WebSocket endpoint of our instance. The connect method attaches the instance we just created to Puppeteer. Then, we simply fetch the webSocketDebuggerUrl value of the created instance. Well, it’s easy to see that we use chrome-launcher in order to launch a Chrome instance manually. Sometimes we want to interact with an existing Chromium instance - whether using puppeteer-core or just attaching a remote instance: Once it’s resolved, we get a browser instance that represents our initialized instance. Notice this method is asynchronous (like most Puppeteer’s methods) which, as we know, returns a Promise.
The launch method initializes the instance at first, and then attaching Puppeteer to that. The easiest way to interact with the browser is by launching a Chromium instance using Puppeteer: This is the reason why Puppeteer’s ecosystem provides methods to launch a new Chromium instance and connect an existing instance also. Naturally, it should have a Chromium instance to interact with. Now, we’re absolutely ready to go! 🤓 Interacting BrowserĪs mentioned before, Puppeteer is just an API over the Chrome DevTools Protocol. Simply run the following to install: npm install puppeteer Once it’s installed, the most recent version of Chromium is placed inside node_modules, what guarantees that the downloaded version is compatible with the host operating system. The main package, called puppeteer, which is actually a full product for browser automation on top of puppeteer-core. In order to install, just run: npm install puppeteer-core
It comes in handy mainly when we don’t need a downloaded version of Chromium, for instance, bundling this library within a project that interacts with a browser remotely. Library PackageĪ lightweight package, called puppeteer-core, which is a library that interacts with any browser that’s based on DevTools protocol - without actually installing Chromium. To begin with, we’ll have to install one of Puppeteer’s packages. Check it out during the article or afterwards. It lets us run Puppeteer scripts every couple of minutes or trigger them from the continuous integration pipeline. In this article we’re going to try out Puppeteer and demonstrate a variety of the available capabilities, through concrete examples.ĭisclaimer: This article doesn’t claim to replace the official documentation but rather elaborate it - you definitely should go over it in order to be aligned with the most updated API specification.Īctive Reliability for Modern DevOps TeamsĬheckly does in-depth API monitoring and synthetic monitoring using Puppeteer.
0 kommentar(er)
