Skip to content

Instantly share code, notes, and snippets.

@balupton
Last active March 8, 2024 18:31
Show Gist options
  • Save balupton/3944017 to your computer and use it in GitHub Desktop.
Save balupton/3944017 to your computer and use it in GitHub Desktop.
Debugging & Profiling Node.js
@paulirish
Copy link

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

@advanced
Copy link

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

@b5
Copy link

b5 commented May 12, 2013

inspect heap snapshots with node-heapdump?

@rizalp
Copy link

rizalp commented May 12, 2013

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

@javruben
Copy link

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

@msolujic
Copy link

@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
Copy link

jkrems commented May 12, 2013

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
Copy link

datio commented Aug 3, 2013

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

@php-cpm
Copy link

php-cpm commented Sep 28, 2016

check it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment