Breakpoints at BrowserWindow Startup (--debug-brk)

[francoislaberge]

I’m having issues where I need to debug some javascript that runs immediately in a BrowserWindow context. I’m running Electron on a remote computer (that doesn’t have it’s own keyboard and can’t) and remote debugging it I can’t get it to pause at the beginning of execution. Is there a way to get behavior like node-inspector’s --debug-brk?

[kierans777]

I had this issue too. It seem like Atom is not respecting the Electron CLI switches.

Atom and Electron CLI switches

I'm using Atom 1.6, which is using Electron 0.34.5. In the Electron docs it mentions the --debug and --debug-brk switches. However running /Applications/Atom.app/Contents/MacOS/Atom --debug-brk=60131 hangs. Normally node processes print out that they're waiting for a listener before proceeding. Using --debug allows Atom to run, but as I'm running a test (--dev --test) I'd like the process to block so I can connect my debugger (WebStorm). Is there something I'm doing wrong?