I don't know what current version of Google Chrome installed. I am using Ubuntu 19.10 eoan and I already have Google Chrome installed and now I want to try puppeteer-core. We will show this later on the source code. Technically we have to define executablePath option that contains the Chrome or Chromium browser path. The difference between puppeteer and puppeteer-core in the term of launch settings is we have to define the Chrome or Chromium browser executable path. I am sure for general use case it will work. And again according to documentation said below.īe sure that the version of puppeteer-core you install is compatible with the browser you intend to connect to. What does it means? It means you can use existing Chrome or Chromium browser for browsing automation with Puppeteer. It available since Puppeteer version 1.7.0. Today we will try to use Puppeteer Core (package name puppeteer-core), a version of Puppeteer that doesn't download Chromium by default. 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.
So it's quite big download size and usually takes long time during installation. log( "CHILD: url received from parent process", url) Ĭonst browser = await puppeteer.If you used to play with Puppetter, you must be already know that when installing Puppeteer (with npm i puppeteer) it will install recent version of Chromium browser. The code snippet below is a simple example of running parallel downloads with Puppeteer.Ĭonst downloadPath = path. 💡 If you are not familiar with how child process work in Node I highly encourage you to give this article a read. We can combine the child process module with our Puppeteer script and download files in parallel. Child process is how Node.js handles parallel programming. We can fork multiple child_proces in Node.
Our CPU cores can run multiple processes at the same time. 💡 Learn more about the single threaded architecture of node here Therefore if we have to download 10 files each 1 gigabyte in size and each requiring about 3 mins to download then with a single process we will have to wait for 10 x 3 = 30 minutes for the task to finish.
It can only execute one process at a time. You see Node.js in its core is a single-threaded system. However, if you have to download multiple large files things start to get complicated.
In this next part, we will dive deep into some of the advanced concepts.
0 kommentar(er)
