Debugging
In Electron apps, the main and renderer processes have different debugging mechanisms:
Renderer processes can be debugged using Chromium DevTools.
The main process can be debugged via the
--inspect
and--inspect-brk
command line flags.
This guide goes over Forge-specific ways of debugging the main process through the command line or with a code editor.
Each section in this guide assumes your package.json
has a "start": "electron-forge start"
script.
For more general information on debugging Electron apps, see the main Electron docs on Application Debugging.
Debugging on the command line
You can specify the --inspect-electron
flag when running electron-forge start
. Internally, this will activate the Electron --inspect
flag, and the main process will listen for a debugging client on port 5858.
Once your app is active, open chrome://inspect
in any Chromium-based browser to attach a debugger to the main process of your app.
To add a breakpoint at the first line of execution when debugging, you can use Forge's --inspect-brk-electron
flag instead.
Debugging with VS Code
To debug the main process through VS Code, add the following Node.js launch configuration:
Once this configuration is added, launch the app via VS Code's Run and Debug view to start debugging.
Debugging with WebStorm or Other Jetbrains IDEs
Access the
Run > Debug...
menu and select theEdit Configurations...
option to open theRun/Debug Configurations
window.Click on the
Add new configuration
button (the+
icon) in the upper-left corner and select thenpm
template.In the
Scripts
dropdown menu, selectstart
.Click on
Debug
to start debugging your app.
Last updated