You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, web-ext uses chrome-launcher@0.15.1, but v1.1.0 was just released, with a fix to make the prefs option work. This enables us to set custom preferences for the profile, including extensions.ui.developer_mode, which would enable developer mode by default when using web-ext, which is super convenient during development.
Just like the --pref for firefox, it would be awesome if we could add --chromium-pref to the CLI and chromiumPrefs to the JS API. Or at least enable extensions.ui.developer_mode by default. I always have to toggle the setting when developing an extension before debugging the background in chrome.
I'd be happy to submit a PR, but I can't get tests to pass after upgrading chrome-launcher, there's a error with the watcher that I can't figure out :/
Version information (for bug reports)
Firefox version: deved 119.0b2
Your OS and version: MacOS Ventura 13.4.1c
Paste the output of these commands:
v18.16.1
9.5.1
7.8.0
The text was updated successfully, but these errors were encountered:
Is this a feature request or a bug?
Feature request.
What is the current behavior?
Currently, web-ext uses
chrome-launcher@0.15.1
, but v1.1.0 was just released, with a fix to make theprefs
option work. This enables us to set custom preferences for the profile, includingextensions.ui.developer_mode
, which would enable developer mode by default when using web-ext, which is super convenient during development.What is the expected or desired behavior?
Just like the
--pref
for firefox, it would be awesome if we could add--chromium-pref
to the CLI andchromiumPrefs
to the JS API. Or at least enableextensions.ui.developer_mode
by default. I always have to toggle the setting when developing an extension before debugging the background in chrome.This might also be a solution for #2874.
I'd be happy to submit a PR, but I can't get tests to pass after upgrading
chrome-launcher
, there's a error with the watcher that I can't figure out :/Version information (for bug reports)
The text was updated successfully, but these errors were encountered: