io.Connect Desktop supports loading additional Chrome extensions and Chrome DevTools extensions into the Chromium used by io.Connect Desktop.
Extensions are configured in the system.json system configuration file of io.Connect Desktop:
- To add regular Chrome extensions, use the
"extensions"top-level key. - To add Chrome DevTools extensions, use the
"devToolsExtensions"top-level key.
Both properties accept a list of URLs pointing to the location of the browser extension.
Q: How do I load a Chrome extension?
Add the extension to the "extensions" top-level key in system.json. The following example demonstrates how to configure io.Connect Desktop to load a regular Chrome extension:
{
"extensions": ["https://path-to-chrome-extension"]
}
Q: How do I load an extension from a local file path?
Available since io.Connect Desktop 9.7
The "extensions" and "devToolsExtensions" top-level keys also accept a list of objects with the following properties:
| Property | Type | Description |
|---|---|---|
"allowFileAccess" |
boolean | If true, will allow the extension to read local files over the file:// protocol and to inject content scripts in local pages. It’s required to set this to true if you want to load an extension from a local file path. Defaults to false. |
"path" |
string | Path to the extension. |
The following example demonstrates how to allow access to the file system in order to load a Chrome extension from a local file path:
{
"extensions": [
{
"path": "C:/path-to-chrome-extension",
"allowFileAccess": true
}
]
}