If you're using Q, you get long stack traces [1] for debugging asynchronous behavior! That way you can follow the entire path of an exception, through multiple

If you're using Q, you get long stack traces [1] for debugging asynchronous behavior! That way you can follow the entire path of an exception, through multiple callbacks. Q also wraps every function with a try/catch statement, and will push caught exceptions into the error pipeline [2]. [1] https://github.com/kriskowal/q#long-stack-traces https://github.com/kriskowal/q#long-stack-traces [2] https://github.com/kriskowal/q#handling-errors https://github.com/kriskowal/q#handling-errors