7 ms·
> Unlike JavaScript in the browser, or Java with a powerful IDE like IntelliJ, you can’t just set breakpoints everywhere I'm using IntelliJ to set breakpoints
by chrisparton1991 8y ago
> Unlike JavaScript in the browser, or Java with a powerful IDE like IntelliJ, you can’t just set breakpoints everywhere
I'm using IntelliJ to set breakpoints everywhere in a Node application at this very moment. It's super easy to set up, you just create a Node.js run configuration and hit the debug button.
- orf 8y agoSame here, but with Python. The IntelliJ debugger is one of the absolute best features and I haven't found anything comparable yet.
- np_tedious 8y agoHow 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"?
- mikewhy 8y agoPretty sure all you need is source maps.
- chrisparton1991 8y agoYep, source maps do the trick.
- np_tedious 8y agolate 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
- snackman7 8y agoYou can do this in VS Code as well. You create a launch.json file, and you can debug. A basic launch.json file is like 3 lines long, and VS Code makes it for you. There's no need for an extension. Maybe the author wasn't aware of that.