[Bug]: Running Chrome using `launchOptions` will lose out to `PLAYWRIGHT_BROWSERS_PATH` under Bazel if `npx playwright install` run about playwright

[pavelfeldman]

What is CHROMIUM_BIN? It is not a part of Playwright or something Playwright supports. You should not call npx playwright install if you are bringing your own browser.

[Aghassi]

@pavelfeldman I realized I mispoke in my initial issue. I appologize.

The issue is that passing the following

          launchOptions: {
            executablePath: process.env.CHROMIUM_BIN,
          },

does not take precedence over playwright_browser_path when I expect it would.

I was using this env and type up my issue wrong. Let me adjust the issue name and context

[pavelfeldman]

What you say below is:

"At runtime, when launching Chromium, use executable located at <CHROMIUM_BIN>."

launchOptions: {
  executablePath: process.env.CHROMIUM_BIN,
},

does not take precedence over playwright_browser_path when I expect it would.

It does take precedence over PLAYWRIGHT_BROWSERS_PATH - the browser from CHROMIUM_BIN will be launched, regardless of the location of the browser registry.

[pavelfeldman]

Closing as per above, please feel free to open a new issue if this does not cover your use case.