The second downside is that with this flag enabled, downloading Chromium/Firefix needs to be tackled outside of puppeteer. That means, we can't set it inside wordpress/scripts to simplify tasks for npm package consumers. 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. PUPPETEERSKIPCHROMIUMDOWNLOAD environment variable (and its variations) needs to be defined in the root of the project. The browser is downloaded to the HOME/.cache/puppeteer folder by default (starting with Puppeteer v19.0.0). Include $HOME/.cache into the project's deployment.įor a version of Puppeteer without the browser installation, see When you install Puppeteer, it automatically downloads a recent version of Chrome for Testing (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 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. |