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 distributed via npm, the Node. Your project folder (see an example below) because not all hosting providers The official Node.js image is a suitable starting point that means you don’t need to manually install Node. Before undertaking any sort of developement, it is highly recommended that you take a look at 16 for the ongoing effort to update this library to avoid duplicating efforts. Heroku, you might need to reconfigure the location of the cache to be within Latest version Released: Project description pyppeteer Note: this is a continuation of the pyppeteer project. 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
0 kommentar(er)
