With a couple of guides explaining how to setup and host a node.js application and the recent addition of experimental support to Heroku, it seems node.js will be a server-side contender. As any server-side application grows it can be harder and harder to track down and manage errors.

The Solution

The Ruby community, along with many others, have long had a solution: Hoptoad. For some reason, I spent a bit of time at RailsConf this past week creating node-hoptoad-notifier. With it you can easily capture and send exceptions to Hoptoad, either with an uncaughtException listener, try/catch block, or manually.

It’s ready for Heroku with support for setting the API key and environment with configuration variables. Unfortunately, Heroku does not appear to currently support the uncaughtException listener.

The Future

I’m excited to see the node.js community growing and evolving so rapidly. I hope to release more libraries and experiments with it over time. And maybe I’ll even pick a side in the emerging package wars soon.