News for hackers. Stuff that matters.

A comment on Visual Studio Code 1.8. Parent comment

Re:Visual Studio Code 1.8 by thenewwazoo on Wednesday December 14, 2016 @05:16PM (#13180166)
I'm not sure why not. AFAIK that's still your only option if you want to debug NodeJS code headlessly.
[ Parent | on HN ]
Re:Visual Studio Code 1.8 by miguelrochefort on Wednesday December 14, 2016 @05:39PM (#13180357)
What about conditional break points, call stack, time travel, watch list, live editing, etc?
[ Parent | on HN ]
Re:Visual Studio Code 1.8 by Ace17 on Thursday December 15, 2016 @01:55AM (#13182956)
Wow, there are actually people using any of these?
[ Parent | on HN ]
Re:Visual Studio Code 1.8 by miguelrochefort on Thursday December 15, 2016 @08:41AM (#13184478)
More like all of these every day?
[ Parent | on HN ]
Re:Visual Studio Code 1.8 by laurencerowe on Wednesday December 14, 2016 @05:45PM (#13180407)
Running 'node debug script.js' will drop you into the command line debugger. It's a little painful though as the command line debugger does not have support for moving up/down stack frames.
[ Parent | on HN ]