From ce45cb8a899ae53999037a5349ad37b4da93bb62 Mon Sep 17 00:00:00 2001 From: Aaron Date: Wed, 23 Apr 2025 23:35:28 -0500 Subject: [PATCH] docs: Add warning about `--load-extension` deprecation --- docs/guide/essentials/config/browser-startup.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/guide/essentials/config/browser-startup.md b/docs/guide/essentials/config/browser-startup.md index c343d810..f1221095 100644 --- a/docs/guide/essentials/config/browser-startup.md +++ b/docs/guide/essentials/config/browser-startup.md @@ -8,6 +8,15 @@ 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: