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 In the end, you should have a list of 3 files, namely, index.js, package-lock.json and package.json, and a nodemodules folder. You’ll also notice that it downloads a recent version of Chromium (170MB Mac, 282MB Linux, 280MB Win) that is guaranteed to work with the API. Heroku, you might need to reconfigure the location of the cache to be within npm install puppeteer This will install Puppeteer from the NPM library. 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). ![]() To skip the download, download into another path, or download a different browser, see Environment variables. When you install Puppeteer, it automatically downloads a recent version ofĬhrome for Testing (~170MB macOS, ~282MB Linux, ~280MB Windows) that is guaranteed to To use Puppeteer in your project, run: npm i puppeteer or 'yarn add puppeteer' 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.
0 Comments
Leave a Reply. |