The browser is downloaded to the HOME/.cache/puppeteer folder by default (starting with Puppeteer v19.0.0). log( "CHILD: url received from parent process", url) Ĭonst browser = await puppeteer. When you install Puppeteer, it automatically downloads a recent version of Chrome for Testing (170MB macOS, 282MB Linux, 280MB Windows) that is guaranteed to work with Puppeteer. 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. Output from some of the examples: codecoverage. We can combine the child process module with our Puppeteer script and download files in parallel. Examples for using Puppeteer to do big, bold things.
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. This is where we will be writing our code to download images from the Bannerbear page. However, if you have to download multiple large files things start to get complicated. In the same project, create index.js file. In this next part, we will dive deep into some of the advanced concepts. Use this online puppeteer playground to view and fork puppeteer example apps and templates on CodeSandbox.
0 kommentar(er)
