Overridable platform via env

[compulim]

While running npm install chromedriver under Linux, some devs may want to install Windows binary instead.

For example, when installing under WSL2, we opt for Windows binary as it will open Chrome in Windows, instead of Chrome in WSLg. And it is okay to run chromedriver.exe (or any .exe) under WSL.

Sidenote, a way to detect if running under WSL or not, is to look at /proc/version and see if it contains keyword "WSL2".

compulim@ubuntu:~$ cat /proc/version
Linux version 5.10.43.3-microsoft-standard-WSL2 (oe-user@oe-host) (x86_64-msft-linux-gcc (GCC) 9.3.0, GNU ld (GNU Binutils) 2.34.0.20200220) #1 SMP Wed Jun 16 23:47:55 UTC 2021

[giggio]

@compulim interesting problem! I work a lot with WSL as well and hadn't thought of this workaround.
I wouldn't do it by default, but an option would be interesting. I usually run chrome headless, so I actually prefer Linux's Chrome.
So, yes, a --force-platform would be interesting. It could take any of the values we use to select the binary. For example, from the current download at https://chromedriver.storage.googleapis.com/index.html?path=94.0.4606.61/, it could be linux64, mac64, mac64_m1, win32.