-
-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable extension developer setting in Chrome automatically in dev mode #137
Comments
This doesn't seem possible. But you can enable it for all profiles, including new ones that WXT creates during dev mode: |
I kept looking into this, and it is possible, but it's blocked by GoogleChrome/chrome-launcher#323.
wxt/src/core/runners/web-ext.ts Line 56 in 89d15ba
import { launch } from 'chrome-launcher';
await webExt.default.cmd.run({
...finalConfig,
chromiumLaunch: (options) => launch({ ...options, prefs: { ... } }),
}, options); |
Can't pass the custom |
This appears to be broken again |
Need to figure out what the new preference is. Old preference: Here's where we can set the new one if we find it: wxt/packages/wxt/src/core/runners/web-ext.ts Lines 96 to 108 in 90bb145
|
Feature Request
When running
wxt
to develop and extension, it's really annoying to have to enable developer mode every time to inspect the different JS contexts of your extension. We should be able to enable it automatically via CLI flags? I assume the switch is just a preference that we can control via CLI flags.Is your feature request related to a bug?
#135
What are the alternatives?
N/A
Additional context
Also a problem with Edge, so we should add the setting to edge and other chromium browsers as well. Hopefully they're all the same internal preference...
The text was updated successfully, but these errors were encountered: