Could not find browser revision 809590

• Puppeteer version: 5.4.1
• Platform / OS version: windows x64 & linux x64
• Node.js version: 15.0.1

With the above config, puppeteer reports

Could not find browser revision 809590

If I just downgrade it to 5.4.0, everything is fine.

[viglucci]

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.

[akaleeroy]

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'
    });