Node inspector has a lot of problems. Buggy as shit. And it's time consuming to use the -brk param to make ur app stop on the first line and then attach node inspector, and then switch back to having it not stop on line 1 when testing ongoing calls. That's why it is important what this guy built to automatically attach itself, even if all the other node inspector bugs still exist. It's particularly hard to find ur files in node inspector and with it refreshing ur always losing where u were, which is also a problem with chrome dev tools but to a lesser extent. I'm generally extremely surprised that node inspector is so shitty. Literally no node developers must debug server side code with a debugger. That's complete idiocy, ie resolving to just log calls throughout ur code. It's a statement of the lack of observability developers are willing to put up with because they know no better. I use node inspector constantly, but it's absolutely retarded how much bullshit I have to sift through. I have to reopen the files I'm working either every single time, drilling deep through file structures, if I don't already have a breakpoint on a file. It doesn't remember what files and folders were open.
I have. I use Meteor, and for Meteor it doesn't support debugging Package code, so that's a no-go for me. But I was impressed by what they were going for in the situations I did get it to work. A few things I miss from the chrome style debugging, but a few new things that were quite useful. In general, debugging for Node needs to be fixed and addressed from the ground-up. It's an afterthought for everyone, which is why we see things happening like chrome dev tools being repurposed. I mean that's not a bad idea, but when the implementation is so clearly a half-assed hack job, it's clear a more foundation-first approach must be done.
It looks like it works by just reusing the devtools that are part of electron instead of shipping it's own (like node-inspector). That might make it more reliable than node-inspector for basic debugging. But that's only a guess after glancing over the code.
