The ongoing collaboration with Mozilla aims to support common end-to-end testing use cases, for which developers expect cross-browser coverage. Official Firefox support is currently experimental. Q: What is the status of cross-browser support? The Chrome DevTools team maintains the library, but we'd love your help and expertise on the project!

Contributing to PuppeteerĬheck out contributing guide to get an overview of Puppeteer development. We really appreciate the hard work those people put in to providing high quality TypeScript definitions for Puppeteer's users. puppeteerrc.cjs (or install -save-dev types that you'll see appearing in the Puppeteer source code are based off the great work of those who have contributed to the package. 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 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

Download puppeteer node for free