Go to your System Preferences > Security & Privacy > General screen, and select Open Anyway. Open Chromium on your machine, and you may receive an alert message as such: If your M1 Mac doesn’t allow third party apps to be open, you may need to give Chromium permission to do so. Step 2: Allow Chromium to open on your M1 Mac The chromium should in the homebrew binary directory, as such: If you want to check which chromium your M1 Mac is using, type the following command: Once you do, open up the terminal and type the following command: Make sure you have Homebrew install on your M1 Mac. Let’s go over how to fix this problem step-by-step.

The answer is to manually install chromium on your machine. Path-to-project/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserFetcher.js:112 If you are on Ubuntu, you can install with: The chromium binary is not available for arm64: To wait for all downloads to complete with Puppeteer using request interception, you can use the request event to intercept all network requests made by the browser and track when they are finished.I recently got the M1 Mac mini computer, and ran yarn or npm to install a project that contained Puppeteer in the package.json file, and I received this error message: Finally, we close the browser instance.īy using the download event, we can wait for all downloads to complete with Puppeteer in a reliable and efficient way. We then navigate to the page that initiates the download and wait for all downloads to complete using the waitForDownload method. We add a listener to the download event to log when a download is completed.

We then set the download behavior for the page to allow downloads and specify the download path. In this code, we first create a new browser instance using Puppeteer and a new page. send ( 'tDownloadBehavior', ) await page. Const puppeteer = require ( 'puppeteer' ) const browser = await puppeteer.

Download puppeteer node