WSL2 should give precedence to Chrome installed on Linux

[igorakkerman]

In WSL2, chrome-launcher running on Linux starts the Chrome instance installed on Windows, even if Chrome is also installed on Linux. IMO the precedence should be changed to prioritize the installation inside of the WSL when no additional arguments are given.

I use WSL2/Ubuntu on Windows 11 and have installed Chrome inside of the WSL. It is on the PATH and I can launch it in the shell using google-chrome.

I tested using the script provided here: https://github.com/GoogleChrome/chrome-launcher#launching-chrome
chrome-launcher version: 0.14.1
Node.js: 17.0.1 / 16.12.0
npm: 8.1.0

[lucacataldo]

For those looking at a temporary solution to this, you can set the CHROME_PATH environment variable to point to your linux install's chrome binary to override the default behaviour which launches the windows executable.

I do agree that when running in WSL, a linux install of Chromium should take precedence by default.

[lucacataldo]

For those looking at a temporary solution to this, you can set the CHROME_PATH environment variable to point to your linux install's chrome binary to override the default behaviour which launches the windows executable.

I do agree that when running in WSL, a linux install of Chromium should take precedence by default.

Actually this doesn't seem to work on WSL2 on Windows 11.

I would say that having a non-null CHROME_PATH environment variable should indicate the user has a preferred chromium binary, especially since Win11 now supports GUI applications natively on WSL.

A simple check for the existence of process.env.CHROME_PATH in chrome-finder.ts should override the check for windows installations.

[avblink]

Bumping this.

[unpWn4bl3]

bump for this