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 Heroku, you might need to reconfigure the location of the cache to be within you might prefer to use Cheerio Scraper, which downloads and processes raw HTML. If you deploy a project using Puppeteer to a hosting provider, such as Render or Puppeteer allows you to work with a browser in headless mode, which allows you to do things like: Create a PDF document and/or an image of a web page. Crawls websites with the headless Chrome and Puppeteer library using a. Puppeteer Browserless Docs Puppeteer Puppeteer is well-supported by browserless, and is easy to upgrade an existing service or app to use it. PreferencesOffline DataChangelogGuideAboutReport a bug. The browser is downloaded to the $HOME/.cache/puppeteer folderīy default (starting with Puppeteer v19.0.0). Puppeteer 7.1.0 API documentation with instant search, offline support, keyboard shortcuts, mobile version, and more. When you install Puppeteer, it automatically downloads a recent version ofĬhrome for Testing (~170MB macOS, ~282MB Linux, ~280MB Windows) that is guaranteed to

Download puppeteer docs for free