puppeteer: Could not find browser revision 809590

A workaround that worked for me was to manually set the executable path using ENV in my dockerfile.

ENV PUPPETEER_EXECUTABLE_PATH="/usr/bin/google-chrome-stable".

Additionally, you might like the https://www.npmjs.com/package/chrome-launcher NPM package which also worked.

No version works, npm installs globally but there’s no Chrome download step.

For example

>npm install -g puppeteer@3.0.0
+ puppeteer@3.0.0
added 49 packages from 79 contributors in 4.594s

Running a puppeteer script dies with:

(node:1416) UnhandledPromiseRejectionWarning: Error: Could not find browser revision 737027. Run "np
m install" or "yarn install" to download a browser binary.
    at ChromeLauncher.launch (C:\Users\pc\AppData\Roaming\npm\node_modules\puppeteer\lib\Launcher.js
:200:23)
    at async startPuppeteer (D:\Dropbox\Agenda\INCFC\Barometru 2019\Practice culturale de timp liber
 in spatii publice\Sources\gulpfile.js:245:15)
    at async exportCharts (D:\Dropbox\Agenda\INCFC\Barometru 2019\Practice culturale de timp liber i
n spatii publice\Sources\gulpfile.js:259:5)

Node.js v13.13.0

I think the problem is npm update no longer downloads and installs Chromium. This fails to happen silently, and it fails on any version of Puppeteer. You think ah I’ll just roll back and it’ll work. But no version does because of this.

Pretty scary bug… 🎃

Workaround

// gulpfile.js
// (...)
browser = await puppeteer.launch({
      // Point to existing Chrome install because NPM won't install Chromium
      executablePath: 'C:/Program Files (x86)/Google/Chrome/Application/chrome.exe'
    });

same here in mac os 10.13.6 chrome 86.0.4240.111 (Official Build) (x86_64) node 14.15.0 puppeteer/-core 5.4.1

setting PUPPETEER_SKIP_DOWNLOAD has no effect

A workaround that worked for me was to manually set the executable path using ENV in my dockerfile.

ENV PUPPETEER_EXECUTABLE_PATH="/usr/bin/google-chrome-stable".

Additionally, you might like the https://www.npmjs.com/package/chrome-launcher NPM package which also workead.

also solved in windows use same method

My issue was on how I was setting the volumes on docker-compose. if I add

   volumes:
      -  ./:/app

It throws that error. Hopefully it helps somebody.

In my case, the solution seems to be just upgrading from Puppeteer v5.4.1 to v9.0.0. That seems to fix it. No need to download a specific Chromium and specify the executablePath.

Try adding the following settings to package.json file.

"config": { "puppeteer_download_path": "./node_modules/puppeteer/.local-chromium" }

In my Windows environment, the above code works.

Same here…