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. Access web browsers, mobile emulators, simulators, and real mobile devices. Include $HOME/.cache into the project's deployment.įor a version of Puppeteer without the browser installation, see The worlds largest continuous testing cloud of web and mobile applications. 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 PreferencesOffline DataChangelogGuideAboutReport a bug. The browser is downloaded to the $HOME/.cache/puppeteer folderīy default (starting with Puppeteer v19.0.0). Puppeteer 7.1.0 API documentation with instant search, offline support, keyboard shortcuts, mobile version, and more. See the Configuration interface for possible options. puppeteerrc.yaml,, and Puppeteer will also read a puppeteer key from your application's package.json. 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 will look up the file tree for any of the following formats.

Download puppeteer docs for free