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 Generally the home directory is well-defined (even on Windows), but occasionally the home directory may not be available. Your project folder (see an example below) because not all hosting providers Starting from v19.0.0, Puppeteer will download browsers into /.cache/puppeteer using os.homedir for better caching between Puppeteer upgrades. 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