![]() 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 Puppeteer is a Node library that provides a high-level API to control headless Chrome, Firefox, and Chromium over the DevTools protocol. ![]() 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 Being an end-user product, puppeteer supports a bunch of convenient PUPPETEER env variables to tweak its behavior. When installed, it downloads a version of Chromium, which it then drives using puppeteer-core. If you deploy a project using Puppeteer to a hosting provider, such as Render or puppeteer is a product for browser automation. 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
0 Comments
Leave a Reply. |