Which is even stranger cause I explicitly used product: 'chrome' in the launch options.Ĭause the executablePath is something like: node_modules/puppeteer/.local-chromium/mac-756035 which does not exist. PUPPETEERPRODUCTfirefox npm install PUPPETEERPRODUCTfirefox yarn install javascript node. “PUPPETEER_PRODUCT=firefox yarn install” to download a supported Firefox browser binary.’ Run 'PUPPETEERPRODUCTfirefox npm install' or 'PUPPETEERPRODUCTfirefox yarn install' to download a supported Firefox browser binary. Run “PUPPETEER_PRODUCT=firefox npm install” or Where as in version 5.4.1 I get a different error:Ĭould not find browser revision 809590. Run “npm install” or “yarn install” to download a browser binary. In version 5.0.0 I get the following error:Ĭould not find browser revision 756035. Tried puppeteer versions 5.0.0 and 5.4.1.At any rate, I hope someone has made a third-party extension in that case. that is surprising to me, as I can't think of a good reason why they wouldn't implement that. I have not set the environment variable to skip the download. Library that provides an API to replay and stringify recordings created using Chrome DevTools Recorder. Puppeteer won't implement this /GoogleChrome/puppeteer/issues/2433 hardkoded at 19:38 Well.When using puppeteer.launch(), I found out it is looking for this folder: node_modules/puppeteer/.local-chromium/mac-756035 which does not exist.

When installing Puppeteer using npm install puppeteer, it does not download a recent version of Chromium as it is mentioned in the documentation.

Download puppeteer github