
Setting product programmatically in puppeteer.launch supersedes this environment variable. This can also be used during installation to fetch the recommended browser binary. PUPPETEER_PRODUCT - specify which browser you'd like Puppeteer to use.PUPPETEER_EXECUTABLE_PATH - specify an executable path to be used in puppeteer.launch.See puppeteer.launch on how executable path is inferred. PUPPETEER_CHROMIUM_REVISION - specify a certain version of Chromium you'd like Puppeteer to use.Defaults to /.local-chromium, where is Puppeteer's package root.
PUPPETEER_DOWNLOAD_PATH - overwrite the path for the downloads folder. Note: this includes protocol and might even include path prefix. PUPPETEER_DOWNLOAD_HOST - overwrite URL prefix that is used to download Chromium. PUPPETEER_TMP_DIR - defines the directory to be used by Puppeteer for creating temporary files. PUPPETEER_SKIP_CHROMIUM_DOWNLOAD - do not download bundled Chromium during installation step. HTTP_PROXY, HTTPS_PROXY, NO_PROXY - defines HTTP proxy settings that are used to download and run the browser. If Puppeteer doesn't find them in the environment during the installation step, a lowercased variant of these variables will be used from the npm config. Puppeteer looks for certain environment variables to aid its operations. For a version of Puppeteer purely for connection, see puppeteer-core. REACT IDLE TIMER TIMEOUT FOR MOZILLA FIREFOX INSTALL
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 (customizable through Environment Variables).