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. Include $HOME/.cache into the project's deployment.įor a version of Puppeteer without the browser installation, see Puppeteer is a headless Node library that provides a high level API for controlling Chromium or.

Your project folder (see an example below) because not all hosting providers The method launches a browser instance with. Heroku, you might need to reconfigure the location of the cache to be within The method initiates a GET request to download the revision from the host. 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). Puppeteer runs headless by default, but can be configured to run full (non-headless) Chrome or Chromium.

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 is a Node library which provides a high-level API to control Chrome or Chromium over the DevTools Protocol.

Download free puppeteer node