4 ms·

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 wa

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/ https://www.jetbrains.com/webstorm/ [2] https://github.com/nodejs/node/commit/14174a95a597cac7b848fe4b3e439814390d6ec6#diff-38574c080d4e2eb38c49b86e6588ad98R64 https://github.com/nodejs/node/commit/14174a95a597cac7b848fe...

jxm262 11y ago
> 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.
- afarrell 11y ago
  ~~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.
  - luv2code 11y ago
    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.
  - timrichard 11y ago
    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-and-profiling-node-js-with-spy-js/ http://blog.jetbrains.com/webstorm/2014/08/tracing-debugging...
luv2code 11y ago
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-community-vs.aspx https://www.visualstudio.com/en-us/products/visual-studio-co... [2] https://github.com/Microsoft/nodejstools https://github.com/Microsoft/nodejstools [3] https://code.visualstudio.com/ https://code.visualstudio.com/
- afarrell 11y ago
  Which CLI debugger are you talking about? I thought one didn't exist
  - drifkin 11y ago
    It has a built-in debugger that you start using `node debug /path/to/script`. See more here: https://nodejs.org/api/debugger.html https://nodejs.org/api/debugger.html
paulirish 11y ago
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 http://crbug.com/174309

jxm262 11y ago

> 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.

afarrell 11y ago
~~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.
- luv2code 11y ago
  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.
- timrichard 11y ago
  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-and-profiling-node-js-with-spy-js/ http://blog.jetbrains.com/webstorm/2014/08/tracing-debugging...

luv2code 11y ago

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-community-vs.aspx https://www.visualstudio.com/en-us/products/visual-studio-co... [2] https://github.com/Microsoft/nodejstools https://github.com/Microsoft/nodejstools [3] https://code.visualstudio.com/ https://code.visualstudio.com/

afarrell 11y ago
Which CLI debugger are you talking about? I thought one didn't exist
- drifkin 11y ago
  It has a built-in debugger that you start using `node debug /path/to/script`. See more here: https://nodejs.org/api/debugger.html https://nodejs.org/api/debugger.html

paulirish 11y ago

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 http://crbug.com/174309