Feature request: add global handling for unhandled promise rejection

As explained at http://thecodebarbarian.com/unhandled-promise-rejections-in-node.js.html, given now “promise heavy” is current api, this is very useful for debugging.

I’d like you to consider:

1. Automatic logging into console of all unhandled promise rejections,
2. Addition of unhandledRejectionEvent event to application, similar to current uncaughtErrorEvent one.

<bountysource-plugin>

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource. </bountysource-plugin>

[sserdyuk]

@tsonevn I am not sure how tracing is related to the subject. Tracing is tracing, error handling is error handling. Right now exceptions inside promise then chains fail silently, and require wrapping all promise calls with catch clauses. While it’s possible to do, it’s burdensome and inefficient. It’s somewhat similar to wrapping all calls in try / catch, which luckily no-one has to do.

[CoreyCole]

Although it might be burdensome to add catch statements everywhere, it’s probably a good idea. Node will soon require that you always catch errors on promises, or it will exit the process

Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

It’s also a good idea because oftentimes you can recover from an error in a catch(). If it was a global catch, the best you could most-likely do would be exit/restart the application