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. When installed, it downloads a version of Chrome, which it then drives using puppeteer-core. Puppeteer is a Node library which provides a high-level API to control Chrome or Chromium over the DevTools Protocol. “PUPPETEER_PRODUCT=firefox yarn install” to download a supported Firefox browser binary.’ puppeteer is a product for browser automation. 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.I have not set the environment variable to skip the download.When using puppeteer.launch(), I found out it is looking for this folder: node_modules/puppeteer/.local-chromium/mac-756035 which does not exist. (Example here) Run with java -jar Lavalink.jar from the same directory. Put an application.yml file in your working directory. When installing Puppeteer using npm install puppeteer, it does not download a recent version of Chromium as it is mentioned in the documentation. Download binaries from the Download Server, GitHub releases (specific versions prior to v3.5 can be found in the CI Server) or GitHub actions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |