Andrey Lushnikov 28d92116b7 feat(puppeteer): support convenience env variables (#3190) ... We had (and still have) a ton of pull requests to support PUPPETEER_EXECUTABLE_PATH and PUPPETEER_CHROMIUM_REVISION in puppeteer launcher. We were hesitant before since env variables are not scoped and thus don't make a good interface for a library. Now, since we determined `puppeteer-core` as a library and `puppeteer` as our end-user product, it's safe to satisfy our user needs. This patch: - teaches PUPPETEER_EXECUTABLE_PATH and PUPPETEER_CHROMIUM_REVISION env variables to control how Puppeteer launches browser - makes sure these variables play no role in `puppeteer-core` package.		2018-09-05 22:59:14 +01:00
..
api.md	feat(puppeteer): support convenience env variables (#3190)	2018-09-05 22:59:14 +01:00
issue_template.md	chore(issue template): Add Node.js version to Issue template(#1683) (#1684)	2017-12-28 14:24:51 -08:00
troubleshooting.md	docs(troubleshooting): add libatk-bridge2.0-0 to ubuntu dependencies (#3096)	2018-08-16 14:46:59 -07:00