Debugging: most often - built in cli debugger + "debugger" keyword (sometimes with "breakOnException" at first breakpoint. I also have small patch in debugger which skips all 'ENOENT' exceptions caused by modules lookup) - https://github.com/sidorares/node-vim-debugger to debug coffee/js mixed code - node-inspector with https://github.com/sidorares/ni wrapper if I need to set a lot of breakpoints/walk stack - https://github.com/sidorares/node-cli-debugger clone of original debugger when I need to change something in debugger logic itself
Profiling: process.hrtime node --prof and tick On Monday, 20 January 2014 03:37:02 UTC+11, wavded wrote: > > Hey everybody, doing a bit of research here and wondering if you can help > me out! > > I personally have benefitted the most from logging, node-webkit-agent > module (perf/memleaks), heapdump module (for prod memleaks), and strace (on > linux) when it comes to debugging Node applications. However, I'm sure > there are tools I haven't used much or had use cases for personally that > are dynamite (like dtrace for instance). I'm curious as to what > tools/techniques you have used AND for what situations were they helpful. > No bad answers here so don't be shy :) > > Thanks much! > Marc > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
