![]() ![]() 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. Package.json "devDependencies": "^7.3.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). I have searched around and found others with this problem, but no solid ways around this. When I do initial npm i I see > install /Users/./node_modules/puppeteerĭownloading Chromium r549031 - 76 Mb 100% 0.0sĬhromium downloaded to /Users/./node_modules/puppeteer/.local-chromium/mac-549031īut this doesn't work and I get the revision error.Īfter I node install.js in Puppeteer's dir, I see Downloading Chromium r637110 - 85.9 Mb 100% 0.0sĬhromium downloaded to /Users/./node_modules/puppeteer/.local-chromium/mac-637110Īny ideas why? This is on macOS & Node 10.15 and I assume it's going to be more difficult to do this in CI. It would seem that npm i with Puppeteer in my deps would be enough, but after install completes, I need to cd into /node_modules/puppeteer then run node install.js to get the correct revision downloaded. Otherwise, when I try to run tests using Puppeteer, I get Error: Chromium revision is not downloaded. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |