Npm WARN enoent ENOENT: no such file or directory, open '/Users/jkr/Downloads/package.json' Npm WARN saveError ENOENT: no such file or directory, open '/Users/jkr/Downloads/package.json' Requesting latest Firefox Nightly version from ĭownloading Firefox Nightly r79.0a1 - 78.2 Mb 100% 0.0sįirefox Nightly (79.0a1) downloaded to /Users/jkr/Downloads/node_modules/puppeteer/.local-firefox/mac-79.0a1 > install /Users/jkr/Downloads/node_modules/puppeteer Let us know how that Downloads % PUPPETEER_PRODUCT=firefox npm i puppeteer You can see an example of this in the Puppeteer install script: (Eventually I expect Puppeteer will download all browsers during its install step, but we're not there yet.)įor the executable path bit, either call executablePath() on the corresponding Puppeteer instance if you can, or you could also create a BrowserFetcher for each product and get path via revisionInfo. How much control do you have over how Karma launches browsers? Perhaps you need to file an issue there.Īnother thing to consider is how Karma installs Puppeteer as a dependency, since Firefox isn't fetched by Puppeteer by default. To use puppeteer v3 for both Firefox and Chrome, I think Karma should create two Puppeteer instances and call launch on each with the appropriate product option. Puppeteer has different Launcher classes for Firefox and Chrome, and an internal state for which launcher is being used. You don't necessarily need PUPPETEER_PRODUCT. What is the recommended way with V3 ? Any upgrade path documented ? Please note the FIREFOX_BIN env var export. FIREFOX_BIN = require ( 'puppeteer-firefox' ). Karma configuration file, see link for more information // const process = require ( 'process' ) process.
0 kommentar(er)
