My fears have been confirmed, everyone trying to jump in early on the NodeJ$ gravy train.
Fixed, albeit temporarily, by adding an uncaughtException event handler on the process object. Will implement a more robust solution in future versions.
An uncaughtException from an event emitted by request is causing the crush, fixing it right away.
Typo: puzzle 11 calls puzzle 10 function
Didn't see this one coming. I'm not sure if the gold rush for commercialising Node and Node related tools like npm is a healthy thing for Node at large.
I got 99 problems but callbacks ain't one (lol, sorry couldn't resist)