We've recently been cleaning up our keyboard shortcut implementation in DevTools. The end goal is definitely enabling customizable shortcuts and we're definitely targeting those step-wise debugging usecases. Star to get updates: http://crbug.com/174309
Also, visual studio community edition is free[1] can debug nodejs with an extension[2]. And the capability is integrated into VS Code[3] which works cross-platform.
Those and webstorm/intellij are the ones I have experience with. But most of the time, I just use the CLI debugger -- it's not hard.
[1] https://www.visualstudio.com/en-us/products/visual-studio-co...
Which CLI debugger are you talking about? I thought one didn't exist
It has a built-in debugger that you start using `node debug /path/to/script`. See more here: https://nodejs.org/api/debugger.html
> node.js requires that you use the browser for debugging
wat? :/
Node.js does not require you to use the browser for debugging. But you're probably referring to node-inspector, which uses Chrome or Opera. I personally find webstorm to be wayyy easier debugging node unit tests specifically.
~~Is webstorm usable outside a jetbrains product? In particular, on a headless server?~~
EDIT: That was a dumb question. This IDE looks pretty cool. I'll check it out. But I still want something that I can run headless.
Re:Chrome Devtools Tips and Tricks
by timrichard on Tuesday October 20, 2015 @07:58AM
(#10418621)
In addition to the standard debugger, WebStorm also give you SpyJS for Node[1], which is a Tracer/Reverse debugger.
[1] http://blog.jetbrains.com/webstorm/2014/08/tracing-debugging...
[1] https://www.jetbrains.com/webstorm/
[2] https://github.com/nodejs/node/commit/14174a95a597cac7b848fe...