web-ext

Different development and build configuration with web-ext

由 我是研究僧i 提交于 2020-05-15 08:46:25
问题 I am working with a browser extension project and want to have a different URL used in background.js during development time and build time. I want to do this without having to remember to change the code between development and build. With a server project I'd simply use dotenv/environment variables but that's not available to extensions which effectively run client side. In background.js I have a fetch using this api_base_url (we develop the API too); ... const api_base_url = 'http://127.0

Chrome WebExtension - Private Store and Enterprise Environment

由 两盒软妹~` 提交于 2019-12-18 07:25:06
问题 I'm trying to publish a Chrome Extension in a Private Store and to propagate it with a Group Policy. In order to do that I'm using the following references: CRX Packaging GPO Propagation I'm 100% sure that the GPO is configured correctly (if I use the same GPO to propagate an extension published on the Chrome WebStore it works). Unfortunately, both my private extension (line in the Configure the list of force-installed apps and extension section: [my_extension_id];[my_xml_url] ) and the

Chrome WebExtension - Private Store and Enterprise Environment

由 筅森魡賤 提交于 2019-11-29 12:56:31
I'm trying to publish a Chrome Extension in a Private Store and to propagate it with a Group Policy. In order to do that I'm using the following references: CRX Packaging GPO Propagation I'm 100% sure that the GPO is configured correctly (if I use the same GPO to propagate an extension published on the Chrome WebStore it works). Unfortunately, both my private extension (line in the Configure the list of force-installed apps and extension section: [my_extension_id];[my_xml_url] ) and the example extension (line: bcanfnleljfidkjhhfknjjiicdonddad;https://sites.google.com/site/pushcrx
订阅 web-ext