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. Please download files in this item to interact with them on your computer. Include $HOME/.cache into the project's deployment.įor a version of Puppeteer without the browser installation, see This item does not appear to have any files that can be experienced on. 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). Puppeteer quick start Install and run Puppeteer. Get started Overview of Puppeteer An explanation of what Puppeteer is and the things it can do. It can also be configured to use full (non-headless) Chrome or Chromium. The browser is downloaded to the HOME/.cache/puppeteer folder by default (starting with Puppeteer v19.0.0). Puppeteer is a Node library which provides a high-level API to control headless Chrome or Chromium over the DevTools Protocol. When you install Puppeteer, it automatically downloads a recent version ofĬhrome for Testing (~170MB macOS, ~282MB Linux, ~280MB Windows) that is guaranteed to When you install Puppeteer, it automatically downloads a recent version of Chrome for Testing (170MB macOS, 282MB Linux, 280MB Windows) that is guaranteed to work with Puppeteer.
0 kommentar(er)
