How do you debug Node.js and what are you missing?

Question

JavaScript

As a Node Inspector developer, I'm interested in the community's opinion on Node.js debugging tools, including:
What are the alternatives, how do they compare favorably?
If you use Node Inspector, what are you missing?
If you've tried Node Inspector and it didn't work, why not?
In connection with the released 0.10.0 release, I am planning a new front of work for myself, which already includes improving the stability of working with iojs, a plugin system, new cli commands ( https://github.com/node-inspector/node-inspector /i... ).
As an example of something that users may miss a lot - asynchronous call stack. (Is it implemented in the debug tools you use?)

Answer 1

I'm ashamed, but I have to admit that I use console.trace, console.dir, console.log for debugging. I need step-by-step debugging generally 2-3 times a year, and what I often need when developing Impress (application server) is monitoring the memory structures inside processes. What I use node-inspector for is to do something like Object.keys(impress.applications.example.cache.files) in the console and get ["/app/examples/access.js", "/app/examples/request .js", "/app/examples/simple/jsonPost.json/post.js", "/app/end.js", "/app/lazy.js"]. This is convenient, but I have never succeeded in putting a breakpoint on the application handler under Impress or somewhere in the Impress system code: handlers crash somewhere in the node system libraries (events, stream, net, fs) in some places , completely unrelated to the breakpoint that I set. If using cluster/fork Impress doesn't start, but thank God I have a 'single' mode where everything happens in one process and so somehow you can dig into the memory. When we finalized Impress to a stable version and released the docks, I was going to take the time to figure out the debugging, dig into these issues and maybe optimize something specifically for compatibility. In general, thanks for the work, sometimes it's very nice! then I was going to take the time and figure out the debugging, dig into these issues and maybe optimize something specifically for compatibility. In general, thanks for the work, sometimes it's very nice! then I was going to take the time and figure out the debugging, dig into these issues and maybe optimize something specifically for compatibility. In general, thanks for the work, sometimes it's very nice!

Answer 2

I am using webstorm. For me, Node Inspector is the second most convenient solution from simple ones, so that I sit down and go. I use it when there is no webstorm.

Answer 3

I use the debug utility