log( 'CHILD: url received from parent process', url) Ĭonst browser = await puppeteer. The templates have to be written in HTML, which makes jsPDF very easy to use for web developers.

The code snippet below is a simple example of running parallel downloads with Puppeteer.Ĭonst downloadPath = path. Puppeteer As you may know, Puppeteer is a Node library that provides a high- level API to control Chrome, but it can also be used to create PDFs as well.

💡 If you are not familiar with how child process work in Node I highly encourage you to give this article a read. Get started Overview of Puppeteer An explanation of what Puppeteer is and the things it can do. It can also be configured to use full (non-headless) Chrome or Chromium. We can combine the child process module with our Puppeteer script and download files in parallel. Puppeteer Puppeteer is a Node library which provides a high-level API to control headless Chrome or Chromium over the DevTools Protocol. 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. Puppeteer is a Node library which provides a high-level API to control headless Chrome or Chromium over the DevTools Protocol. In this next part, we will dive deep into some of the advanced concepts.

Download free puppeteer docs