electron-extensions will allow you to use Chrome extensions APIs with Electron.
$ npm install electron-extensionsThe library is really easy-to-use. All you have to do is to put the following code in your main process:
import { ExtensibleSession } from 'electron-extensions/main';
import { app } from 'electron';
const extensions = new ExtensibleSession();
(async () => {
await app.whenReady();
extensions.loadExtension('C:/.../abcdefghijklmnoprstuwxyz'); // Path to the extension to load
})();optionsobjectpartitionstring - By defaultnull. It's used for injecting preloads to loadcontent_scriptsin all webContents within a given Electronsession. Must be called inappreadyevent.preloadPathstring - Path to content preload script. The option can be useful for bundlers likewebpackif you're usingCopyWebpackPlugin.blackliststring[] - List of URLs or glob patterns preventing from injectingcontent_scriptsto. For example[wexond://*/*].
It's only for the main process. It's used to load extensions and handle their events.
Loads an extension from a given path.
Adds a BrowserWindow to send and observe UI related events such as
chrome.browserAction.onClicked
List of URLs or glob patterns preventing from injecting content_scripts to. For example [wexond://*].
Emitted when chrome.browserAction.setBadgeText has been called in an extension.
Returns:
extensionIdstringdetailschrome.browserAction.BadgeTextDetails
Emitted when chrome.tabs.create has been called in an extension.
import { extensionsRenderer } from 'electron-extensions';
extensionsRenderer.on('create-tab', (details, callback) => {
const tab = createTab(details); // Some create tab method...
callback(tab.id);
});Returns:
detailschrome.tabs.CreatePropertiescallback(tabId: number) => void - Must be called with the created tab id as an argument. Also, thetabIdmust be the same as any attachedwebContentsid
import { extensionsRenderer } from 'electron-extensions/renderer';Emits chrome.browserAction.onClicked event in a given extension.