News for hackers. Stuff that matters.

A comment on The Absolute Easiest Way to Debug Node.js – With VS Code. Parent comment

Re:The Absolute Easiest Way to Debug Node.js – With VS Code by np_tedious on Monday November 12, 2018 @08:43AM (#18432525)
How does this work with transpilation? Say I have typescript or a just different js than the end build, how does the debugger know which line to put the breakpoint on?

Does the run config need to be something more structured than "run this gulp command"?

[ Parent | on HN ]
Re:The Absolute Easiest Way to Debug Node.js – With VS Code by mikewhy on Monday November 12, 2018 @10:27AM (#18433136)
Pretty sure all you need is source maps.
[ Parent | on HN ]
Re:The Absolute Easiest Way to Debug Node.js – With VS Code by chrisparton1991 on Tuesday November 13, 2018 @06:39PM (#18445935)
Yep, source maps do the trick.
[ Parent | on HN ]
Re:The Absolute Easiest Way to Debug Node.js – With VS Code by np_tedious on Wednesday November 21, 2018 @09:14AM (#18502790)
late response, but i just got stop debugging for a typescript/node app set up in webstorm. far easier than i (and this article) had built it up to be. the sourcemap stuff was actually already taken care of, it was the addition of `$NODE_DEBUG_OPTION` to the `ts-node-dev` command that did the trick
[ Parent | on HN ]