feat: Add DisableLoadExtensionCommandLineSwitch flag to Chromium runner (#1698)
This commit is contained in:
@@ -8,16 +8,6 @@ outline: deep
|
||||
|
||||
During development, WXT uses [`web-ext` by Mozilla](https://www.npmjs.com/package/web-ext) to automatically open a browser window with your extension installed.
|
||||
|
||||
:::danger
|
||||
Chrome 137 removed support for the `--load-extension` CLI flag, which WXT relied on to open the browser with an extension installed. So this feature will not work for Chrome.
|
||||
|
||||
You have two options:
|
||||
|
||||
1. Install [Chrome for Testing](https://developer.chrome.com/blog/chrome-for-testing/) (which still supports the `--load-extension` flag) and [point the `chrome` binary to it](#set-browser-binaries), or
|
||||
2. [Disable this feature](#disable-opening-browser) and manually load your extension
|
||||
|
||||
:::
|
||||
|
||||
## Config Files
|
||||
|
||||
You can configure browser startup in 3 places:
|
||||
|
||||
@@ -55,6 +55,7 @@ export function createWebExtRunner(): ExtensionRunner {
|
||||
),
|
||||
args: [
|
||||
'--unsafely-disable-devtools-self-xss-warnings',
|
||||
'--disable-features=DisableLoadExtensionCommandLineSwitch',
|
||||
...(wxtUserConfig?.chromiumArgs ?? []),
|
||||
],
|
||||
}),
|
||||
|
||||
Reference in New Issue
Block a user