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. For a version of Puppeteer without installation, see puppeteer-core. Include $HOME/.cache into the project's deployment.įor a version of Puppeteer without the browser installation, see To use Puppeteer in your project, run: npm i puppeteer or yarn add puppeteer or pnpm i puppeteer When you install Puppeteer, it automatically downloads a recent version of Chromium (170MB macOS, 282MB Linux, 280MB Windows) that is guaranteed to work with Puppeteer. 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 To use Puppeteer in your project, run: npm i puppeteer or using yarn yarn add puppeteer or using pnpm pnpm i puppeteer. First make a directory which you will be working with by right clicking on your preferred location and choosing new folder. 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 is a Node.js library which provides a high-level API to control Chrome/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
0 Comments
Leave a Reply. |