You've been using Node wrong all along
Well up until recently, I've been using Node the hard way. I had to generously sprinkle in console log messages to track down where things were broken. I had a sense this was the wrong way of doing things, but I just wanted to debug fast and didn't want to spend time looking into the debugging technologies available.
I didn't save any time skipping this step.
sudo npm install -g node-inspector
You can run and use the tool with two separate commands once its installed. First, start the inspector:
Then run your node script using node-debug:
Anyone who uses Chrome's Developer tools will feel right at home inside the Node Inspector, and if you have any familiarity with web inspectors in general, this paradigm should be recognizable. Here is what it looks like:
I've only been using it for a little while, but so far I love it and I've decided I was nuts to try using Node without it. Give it a try, you should be able to get it up and running in 5 minutes.
* Blink is Chrome's fork of WebKit, which I haven't really noticed much differentiation from yet.