News for hackers. Stuff that matters.
Re:Chrome Devtools Tips and Tricks by jxm262 on Monday October 19, 2015 @10:11PM (#10417028)
> 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.

Re:Chrome Devtools Tips and Tricks by afarrell on Monday October 19, 2015 @11:13PM (#10417202)
~~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...

Re:Chrome Devtools Tips and Tricks by luv2code on Monday October 19, 2015 @11:49PM (#10417313)
Since debugging is over a TCP connection, you only have to start the nodejs process with the debug flag, and then plug the address and port into whatever debugger you're trying to use.