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. Puppeteer is a headless Node library that provides a high level API for controlling Chromium or. Puppeteer uses several defaults that can be customized through configurationįor example, to change the default cache directory Puppeteer uses to installīrowsers, you can add a. Step 1: Install chromium with Homebrew Make sure you have Homebrew install on your M1 Mac. Puppeteer version: 1.17.0, 1.18.0, 1.18.1, 1.19.0. Include $HOME/.cache into the project's deployment.įor a version of Puppeteer without the browser installation, see Please refer to the below article written by one of our Team members. We have seen similar issues with puppeteer not working with Function Windows platform. For Function app on windows, it might be hitting the sandbox limitation. Your project folder (see an example below) because not all hosting providers Dec 28, 2022, 4:19 AM Puppeteer is node.js library to control chromium and it would work with Linux platforms. Heroku, you might need to reconfigure the location of the cache to be within

If you deploy a project using Puppeteer to a hosting provider, such as Render or

The browser is downloaded to the $HOME/.cache/puppeteer folderīy default (starting with Puppeteer v19.0.0). When you install Puppeteer, it automatically downloads a recent version ofĬhrome for Testing (~170MB macOS, ~282MB Linux, ~280MB Windows) that is guaranteed to

Puppeteer node download