debugging - node debug plus lots of small unit and functional tests I can step through in the debugger, bunyan, console.log, mdb (especially for postmortem) profiling - dtrace + flame graphs (it's been a while since node --prof gave me actionable information) benchmarking - more dtrace, lots of simple ops/second node snippets, node --trace-opt, node --trace-deopt --code-comments, IRHydra (when I really need it -- I always forget how to use it and need to relearn)
Also, this may sound so obvious as to be almost condescending, but I've learned it's not obvious to many people -- having the source to everything you're using available and reviewing it when code isn't behaving as expected is often the fastest way to isolate problems. This is just as true for working with node itself as with modules. Of these tools, I use node debug and my test suites the most by far. I don't think it's an exaggeration to say I've logged hundreds of hours in the node debugger. Since I'm running through the same test cases over and over, trying to isolate where things go off the rails, the overhead of dealing with node-inspector is too much of a hassle to be worth it. It kind of sucks, but for the weird corner cases I seem to spend most of my time ironing out, it's the best thing I've got. On Sunday, January 19, 2014, wavded <[email protected]> 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]<javascript:_e({}, 'cvml', '[email protected]');> > To unsubscribe from this group, send email to > [email protected] <javascript:_e({}, 'cvml', > 'nodejs%[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] <javascript:_e({}, 'cvml', > 'nodejs%[email protected]');>. > For more options, visit https://groups.google.com/groups/opt_out. > -- -- 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.
