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 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 The Chrome DevTools protocol is an API specification that allows you to interact with the Chromium and Blink-based browsers. Puppeteer allows us to write the tests using Javascript or Typescript. If you deploy a project using Puppeteer to a hosting provider, such as Render or Puppeteer is a NodeJS-based framework, it is Open source and maintained by Google. 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 js download