public
balupton / README.md
Last active

Debugging & Profiling Node.js

  • Download Gist
ttezel commented

thanks for this list - helpful!

cherifya commented

Very helpful indeed. Thanks!

kevireilly commented

Just a heads up regarding the Nodetime: they now require an accountKey that you need to get by signing up at their web site.

rizwaniqbal commented

great resource :+1::feelsgood:

passy commented

There's also traceGL now: https://trace.gl/

shaoyuan1943 commented

Very good,thank you!

muhammadghazali commented

Cool!
Thank you.

teltploek commented

Thank you!

balupton commented

Wow, traceGL seems amazing! Added it to the list :) Also added downgrade information for node-inspector

bjkim commented

Good job! thanks :)

paulirish commented

Flame Charts just landed in Chrome DevTools (cpu profiler) so porting them into node-webkit-agent should actually be fairly easy. cc @c4milo

advanced commented

@paulirish can't seem to find the option in the cpu profiler. are you using chrome canary?

brendanobrienesq commented

inspect heap snapshots with node-heapdump?

rizalp commented

Awesome. Is there any way we can integrate these tools with Sublime Text?

javruben commented

Cloud9 IDE (c9.io) comes with a Node.js debugger.

msolujic commented

@balupton great list of tools.

For those of us who come from Eclipse comfort, debugging can be a lot like you are used to with JVM: https://github.com/joyent/node/wiki/Using-Eclipse-as-Node-Applications-Debugger

jkrems commented

Shameless plug: I'm currently working on a something that's pretty similar (and started as a fork of) to node-inspector [1]. It could be interesting for people using coffee-script since it has support for source maps. And it works with the built-in DevTools that ship with Chrome.

[1] https://github.com/jkrems/bugger

datio commented

You might want to edit your SO answer by adding Google WTF.

Please sign in to comment on this gist.

Something went wrong with that request. Please try again.