Puppeteer and Playwright each support a different set of browsers. It's interesting to note that some of the folks who worked on Puppeteer are now working on Playwright. Google maintains Puppeteer and Microsoft maintains Playwright. More recently, Puppeteer and Playwright have gained in popularity. Selenium WebDriver was a pioneer in this space. Browser automation with Puppeteer and Playwrightīrowser automation has been around for a long time. This enables some serverless browser automation scenarios using popular frameworks such as Puppeteer and Playwright. log( 'CHILD: url received from parent process', url) Ĭonst browser = await puppeteer.With a recent update to Azure Functions, it is now possible to run headless Chromium in the Linux Consumption plan. 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.

Puppeteer download