6/5/2023 0 Comments Puppeteer npm downloadI 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. To skip the download, download into another path, or download a different browser, see Environment variables. 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. 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. Being a library, puppeteer-core is fully driven through its programmatic interface implying no defaults are assumed and puppeteer-core will not download Chromium when installed. There are 5810 other projects in the npm registry using puppeteer. Otherwise, when I try to run tests using Puppeteer, I get Error: Chromium revision is not downloaded. Start using puppeteer in your project by running npm i puppeteer.
0 Comments
Leave a Reply. |