Since version 1.7.0 we publish the puppeteer-core package,a version of Puppeteer that doesn't download Chromium by default. To skip the download, see Environment variables. 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. Note: When you install Puppeteer, it downloads a recent version of Chromium (170MB Mac, 282MB Linux, 280MB Win) that is guaranteed to work with the API. Since version 1.7.0 we publish the puppeteer-core package, a version of Puppeteer that doesn't download Chromium by default. Include $HOME/.cache into the project's deployment.įor a version of Puppeteer without the browser installation, see Note: When you install Puppeteer, it downloads a recent version of Chromium (170MB Mac, 282MB Linux, 280MB Win) that is guaranteed to work with the API. Your project folder (see an example below) because not all hosting providers Now use npm to install Puppeteer: npm install -save puppeteer This command installs both Puppeteer and a version of Chromium that the Puppeteer team knows will work with their API. 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
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |