We could follow this path for however, this doesn't solve the issue that installing one of those packages will download Chromium/Firefox on npm installl. Instead, it asks the package consumer to install puppeteer or puppeteer-firefox depending on which browser they would like to use. As of today in their master branch they have PR landed feat: support 'browser' config option argos-ci/jest-puppeteer#220 which removes peerDependency on puppeteer. jest-puppeteer is about to enable support for Firefox.Or: Simply calling npm install as a synchronous subprocess in the script(s) itself. Some brief searching yielded few results: There may be a module we could leverage for this purpose. Updating end-to-end test scripts to install Puppeteer / download Chromium if not already installed / downloaded.See PUPPETEER_SKIP_CHROMIUM_DOWNLOAD environment variable.Or otherwise instructing Puppeteer installer to not yet download Chromium.Still as an optionalDependencies ? Or not at all mentioned.Removing puppeteer as an explicit dependency.as part of the end-to-end scripts themselves. One option may be to lazily download Puppeteer only when necessary, i.e. ⇒ npm i Chromium r575458 - 80.4 Mb 99% 0.0sĬhromium downloaded to /Users/andrew/Documents/Code/rememo/node_modules/puppeteer/.local-chromium/mac-575458

Free download puppeteer docs