![]() ![]() ![]() Which is even stranger cause I explicitly used product: 'chrome' in the launch options.Ĭause the executablePath is something like: node_modules/puppeteer/.local-chromium/mac-756035 which does not exist. “PUPPETEER_PRODUCT=firefox yarn install” to download a supported Firefox browser binary.’ Once you have a solid understanding of Puppeteer’s API and how it fits together in the Node. Step 1: Install chromium with Homebrew Make sure you have Homebrew install on your M1 Mac. 1.20.0 Platform / OS version: Linux, 64bit, Ubuntu 19.10 URLs (if applicable): (the chromium artifact being downloaded) Node.js version: v12.16.1, v12.16.0, v12.13. ![]() ![]() Run “PUPPETEER_PRODUCT=firefox npm install” or There are many ways you can download files with Puppeteer. Puppeteer version: 1.17.0, 1.18.0, 1.18.1, 1.19.0. Where as in version 5.4.1 I get a different error:Ĭould not find browser revision 809590. Run “npm install” or “yarn install” to download a browser binary. In version 5.0.0 I get the following error:Ĭould not find browser revision 756035. Tried puppeteer versions 5.0.0 and 5.4.1.I have not set the environment variable to skip the download.When using puppeteer.launch(), I found out it is looking for this folder: node_modules/puppeteer/.local-chromium/mac-756035 which does not exist. Method 1: Set the Download Behavior To download a file with Puppeteer using headless mode, you can set the download behavior using the () method. It’s basically a browser which you can run from Node.js. Puppeteer runs headless by default, but can be configured to run full (non-headless) Chrome or Chromium. When installing Puppeteer using npm install puppeteer, it does not download a recent version of Chromium as it is mentioned in the documentation. Puppeteer is a Node library which provides a high-level API to control Chrome or Chromium over the DevTools Protocol. ![]()
0 Comments
Leave a Reply. |