Josh Bielick 6d6ea9bf59 fix: always use ENV executable path when present (#7985) ... Some recent changes to allow arm64 environments (including M1 macs) to launch a chromium installation successfully before arm-compatible builds were downloadable prevented the usage of PUPPETEER_EXECUTABLE_PATH in some environments. Currently, when the platform is not darwin and the arch is arm64, an executable cannot be specified using the environment variable. Generally speaking, environment variables have highest precedence for options such as this since they depend on system configuration. These change: 1. allow the ENV variable to always be used when defined and not specified in LaunchOptions (and when not puppeteer-core) 2. Retain the existing behavior of assuming /usr/bin/chromium-browser on platforms like Ubuntu (exact if-conditions preserved to avoid any breaking changes) 3. Add some tests for this particular portion of the code.		2022-02-11 13:07:31 +00:00
..
BrowserFetcher.ts	revert: esm modules (#7996)	2022-02-10 13:34:36 +00:00
BrowserRunner.ts	fix: try to remove the temporary user data directory after the process has been killed (#7761)	2021-11-15 11:52:09 +00:00
install.ts	fix: make more files work in strict-mode TypeScript (#7936)	2022-01-28 09:38:36 +00:00
Launcher.ts	fix: always use ENV executable path when present (#7985)	2022-02-11 13:07:31 +00:00
LaunchOptions.ts	fix: clearer jsdoc for behavior of headless when devtools is true (#7748)	2021-11-16 21:31:24 +01:00
NodeWebSocketTransport.ts	revert: esm modules (#7996)	2022-02-10 13:34:36 +00:00
PipeTransport.ts	chore: enforce file extensions on imports (#6202)	2020-07-13 10:22:26 +01:00
Puppeteer.ts	fix: make projectRoot optional in Puppeteer and launchers (#7967)	2022-02-07 12:59:44 +01:00