News for hackers. Stuff that matters.
Re:Chrome Devtools Tips and Tricks by afarrell on Monday October 19, 2015 @09:55PM (#10416982)
The author's frustration with the lack of customizable shortcuts is my biggest issue with chrome devtools as well. This is especially frustrating when I just want to pop a debugger statement in the middle of a node.js unit test so I can step through things, but node.js requires that you use the browser for debugging. (EDIT: apparently there is an IDE from jetbrains[1] that lets you do this too) This past Friday I started poking around to see what it would take to write a terminal-based browser in the style of the python debugger and found that the v8 team at Google has been working making the debugger separable from the browser since at least February of this year[2].

[1] https://www.jetbrains.com/webstorm/

[2] https://github.com/nodejs/node/commit/14174a95a597cac7b848fe...

Re:Chrome Devtools Tips and Tricks by paulirish on Tuesday October 20, 2015 @04:55AM (#10418125)
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
Re:Chrome Devtools Tips and Tricks by luv2code on Monday October 19, 2015 @11:42PM (#10417295)
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...

[2] https://github.com/Microsoft/nodejstools

[3] https://code.visualstudio.com/

Re:Chrome Devtools Tips and Tricks by afarrell on Tuesday October 20, 2015 @01:49AM (#10417638)
Which CLI debugger are you talking about? I thought one didn't exist
Re:Chrome Devtools Tips and Tricks by drifkin on Tuesday October 20, 2015 @03:25AM (#10417883)
It has a built-in debugger that you start using `node debug /path/to/script`. See more here: https://nodejs.org/api/debugger.html
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.