Use Chromium's available versions to find the stable version of ChromeDriver

[benjaminapetersen]

It would be most helpful if configuration could be committed to code (and then version control). Simply put, I'd like to be able to assert versions in package.json or a webdrivermanager.json config file. Running webdriver-manager update & getting whatever drivers & version of selenium happens to install is concerning as it makes it difficult to trust the e2e setup (did a version change, or was it a test flake?). I realize you can pass flags to webdriver-manager. Thats a good start, but perhaps one more layer of polish?

[cnishina]

You could pass flags to control the versions being downloaded. Also this is well documented in the repo. I'm not exactly sure what this extra layer would do. It is not clear how this issue could be turned into a feature.

[cnishina]

I think a webdrivermanager.json could be interesting. Kind of like freezing the dependencies like a npm lock on binaries. I do not have the bandwidth to get this done any time soon...

[benjaminapetersen]

Exactly.

Is tempting to look, but I'd prob hesitate to take a stab @ a PR w/o some suggested direction from anyone more core to the project.

[cnishina]

This seems reasonable to read a file and use this file for versions. Maybe this could also be tied into pinning a version. So webdriver-manager might have a default version json file (at least to pin chromedriver to the version 73) and a user can define their own webdriver-manager json file.

When 74 is released, we will need to remove the pinned version from the repo and let users define their own json file. This could just be used just in case we run into the current chrome + chromedriver version mismatch.

[cnishina]

From a previous comment in #306:

we will support a config file for pinning downloads and also starting the server. Instead of checking the file for the last version downloaded we could refer to the config first