The problem here is that IPC communication becomes tricky, as the main process sends messages to the BrowserWindow, and it's not possible afaik to send messages directly to the dev-tools/extension... so some kind of bridge is required.
UI can be fully reused, as it's designed to look like the dev-tools native interface.
Even an optional field in the options object could be provided to toggle the UI between BrowserWindow and devToolPanel (since it's already implemented)...
Continue the original approach for this package and provide the UI not as a
BrowserWindow, but as part of the dev-tools native UI (for better integration).The problem here is that IPC communication becomes tricky, as the main process sends messages to the
BrowserWindow, and it's not possible afaik to send messages directly to the dev-tools/extension... so some kind of bridge is required.UI can be fully reused, as it's designed to look like the dev-tools native interface.
Even an optional field in the options object could be provided to toggle the UI between
BrowserWindowanddevToolPanel(since it's already implemented)...