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. It requires zero setup and comes bundled with the Chromium version most suited to it. Include $HOME/.cache into the project's deployment.įor a version of Puppeteer without the browser installation, see Downloads: 4 This Week Last Update: 3 days ago Download Summary Files Reviews Puppeteer is a headless Node library that provides a high level API for controlling Chromium or Chrome over the DevTools protocol. Your project folder (see an example below) because not all hosting providers 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 type download