Electron supports the Chrome DevTools Extension, which can be used to extend the ability of devtools for debugging popular web frameworks.
How to load a DevTools Extension
This document outlines the process for manually loading an extension. You may also try electron-devtools-installer, a third-party tool that downloads extensions directly from the Chrome WebStore.
To load an extension in Electron, you need to download it in Chrome browser,
locate its filesystem path, and then load it by calling the
Using the React Developer Tools as example:
- Install it in Chrome browser.
- Navigate to
chrome://extensions, and find its extension ID, which is a hash string like
- Find out filesystem location used by Chrome for storing extensions:
- on Windows it is
- on Linux it could be:
- on macOS it is
- on Windows it is
- Pass the location of the extension to
BrowserWindow.addDevToolsExtensionAPI, for the React Developer Tools, it is something like:
const path = require('path') const os = require('os') BrowserWindow.addDevToolsExtension( path.join(os.homedir(), '/Library/Application Support/Google/Chrome/Default/Extensions/fmkadmapgofadopljbjfkapdkoienihi/0.15.0_0') )
BrowserWindow.addDevToolsExtension API cannot be called before the
ready event of the app module is emitted.
The name of the extension is returned by
and you can pass the name of the extension to the
API to unload it.
Supported DevTools Extensions
Electron only supports a limited set of
chrome.* APIs, so some extensions
chrome.* APIs for chrome extension features may not work.
Following Devtools Extensions are tested and guaranteed to work in Electron:
- Ember Inspector
- React Developer Tools
- Backbone Debugger
- jQuery Debugger
- AngularJS Batarang
- Vue.js devtools
- Cerebral Debugger
- Redux DevTools Extension
- MobX Developer Tools
What should I do if a DevTools Extension is not working?
First please make sure the extension is still being maintained, some extensions can not even work for recent versions of Chrome browser, and we are not able to do anything for them.
Then file a bug at Electron's issues list, and describe which part of the extension is not working as expected.