introduce puppeteer-core package

Puppeteer automatically downloads Chrome. This is great, I wish I could use this feature for my tests running in Karma as well, and there are probably more use cases.

I think it would be nice if the Chrome downloader would be extracted from puppeteer, so more tools can depend on it. The export should probably just be the path of the node executable.

E.g.:

const chromePath = require('chrome')

console.log(chromePath) // Something like '/app/node_modules/chrome/bin' or '/app/node_modules/.bin/google-chrome'

[aslushnikov]

puppeteer-core has been published since v1.7.0.

[yanivefraim]

@aslushnikov -

I guess we’re not only ones to have this problem:

https://github.com/travis-ci/travis-ci/issues/5676

I’m still trying to find a way to run two different deployments from one repo/package using Travis’ provider: npm. Not sure this is possible.

The alternatives (as far as I can tell) are:

1. Run puppeteer deploy as it is today (via Travis’ provider: npm) + have another script for deploying puppeteer-core
2. Run both deployments using a script (Travis’ deploy: script feature or just adding a 'deploy` script to package.json scripts)

Any thoughts (maybe I miss something here)?

P.S: just making sure - our release versions are being run manually?