straker / browser-driver-manager Goto Github PK

There is a small window of time where Chromedriver beta gets a new release and is then 2 versions ahead of the npm version and causes the build to fail. Need to implement some sort of fallback for these scenarios as to allow tests to continue to work while the npm version plays catchup.

Chrome Beta version detected as Google Chrome 102.0.5005.27 beta
Installing ChromeDriver 102
log: Received response of 100.0.0
ChromeDriver 102 not found. Retrying with ChromeDriver 101
browser-driver-manager error: Unable to get ChromeDriver version; Something went wrong

Exited with code exit status 1

A lot of packages use $CHROME_BIN env variable as the path to the Chrome executable. See puppeteer/puppeteer#9418 and https://github.com/actions/runner-images/blob/main/images/linux/scripts/installers/google-chrome.sh#L39

Furthermore, Karma supports using CHROME_CANARY_BIN to run Chrome Canary https://github.com/karma-runner/karma-chrome-launcher

When installing Chrome and ChromeDriver, should list the paths that each were found / installed to (even in non-verbose settings).

With the release of Chrome for Testing, the Chrome team has changed how and where they host their executables. The install path for latest chromedriver is no longer supported at https://chromedriver.storage.googleapis.com/LATEST_RELEASE_. The new way to do this is to use the JSON endpoints.

However, the JSON endpoints are massive and will only grow over time (they list all versions since it was ported over [v113]), so it would be better to use the other APIS which follow the LATEST_RELEASE_ format and return a very small amount of information.

It looks like when trying to use this as an NPM script in Ubuntu CI there is a type issue where cursorTo() is not a function.

process.stdout.cursorTo(lastChunk.length - 1);
                       ^
TypeError: process.stdout.cursorTo is not a function