Hence, if you build the application from a Linux environment to a WIndows environment, it won't find Chromium (as Chromium for windows hasn't been installed). However, only the Chromium version corresponding to your current platform would be downloaded.

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. What you said is correct as Chromium is been downloaded when you install puppeteer via npm. Step 3 Launch the Visual Studio Code application and click on the. Include $HOME/.cache into the project's deployment.įor a version of Puppeteer without the browser installation, see Step 2 Create an empty folder, say puppeteer in a location. Download and install Node.js Install Puppeteer Install Mocha Install Chai Install Selenium Webdriver You only need to complete the last step if you want to run tests on an actual browser instead of just testing against web driver scripts. 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). Puppeteer is distributed via npm, the Node.js package manager.

When you install Puppeteer, it automatically downloads a recent version ofĬhrome for Testing (~170MB macOS, ~282MB Linux, ~280MB Windows) that is guaranteed to

Puppeteer npm download