You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Sven Slootweg e3b614cd7d Fix path in testing script 4 years ago
src Initial commit 4 years ago
test Fix path in testing script 4 years ago
.babelrc Initial commit 4 years ago
.gitignore .gitignore created by brackets-git extension 4 years ago
.npmignore Initial commit 4 years ago Initial commit 4 years ago Initial commit 4 years ago
gulpfile.js Initial commit 4 years ago Initial commit 4 years ago
index.js Initial commit 4 years ago
package.json Initial commit 4 years ago
webpack.config.browser.js Initial commit 4 years ago
webpack.config.webworker.js Initial commit 4 years ago


Unfortunately, there’s quite a bit of variation between different Promises implementations and environments, in how you are supposed to (globally) detect unhandled rejections. This can make it tricky to reliably log such errors, especially in browsers.

This module provides a single unified API for detecting unhandled rejections (and their subsequent handling, if any). It works in Browserified/Webpacked environments as well, as long as the Promises implementations support it.

Don’t ignore unhandled errors. This module is meant to be used for implementing log-and-crash logic - once an unexpected error (ie. bug) occurs, it is not safe to continue, as your application is now in an unpredictable state. You should instead let your application crash after logging the error, to start over with a ‘clean slate’.

Supported implementations

If your favourite Promises implementation or environment is not (correctly) supported by this module yet, please open a ticket!

Node.js WebWorkers Modern browsers Old browsers
Bluebird (> 2.7.0)
ES6 Promises (Node.js)¹ n/a n/a n/a
ES6 Promises (WHATWG)² n/a n/a
WhenJS ✓⁴ ✓⁴
(other, per spec)³ n/a n/a n/a
Symbol Meaning
Implemented and supported.
Not implemented - library does not support global rejection events in this environment.
n/a Specification does not cover this environment.
¹ Node.js implementation
² WHATWG specification
³ @benjamingr’s specification
Implementation exists, but is currently completely broken in bundled environments, such as Webpack and Browserify. (issue)


WTFPL or CC0, whichever you prefer. A donation and/or attribution are appreciated, but not required.


Maintaining open-source projects takes a lot of time, and the more donations I receive, the more time I can dedicate to open-source. If this module is useful to you, consider making a donation!

You can donate using Bitcoin, PayPal, Flattr, cash-in-mail, SEPA transfers, and pretty much anything else. Thank you!


Pull requests welcome. Please make sure your modifications are in line with the overall code style, and ensure that you’re editing the files in src/, not those in lib/.

Build tool of choice is gulp; simply run gulp while developing, and it will watch for changes.

Be aware that by making a pull request, you agree to release your modifications under the licenses stated above.

Make sure to read the beforehand. The various unhandledRejection APIs are extremely finicky, and it’s tricky to work out exactly how you can make everything play together nicely. When making a pull request, make sure to intensively check that you haven’t broken anything in the process.


const unhandledRejection = require("unhandled-rejection");

// Assuming `loggingServer` is some kind of logging API...

let rejectionEmitter = unhandledRejection({
	timeout: 20

rejectionEmitter.on("unhandledRejection", (error, promise) => {

rejectionEmitter.on("rejectionHandled", (error, promise) => {

Rejections and timeouts

Due to the asynchronous nature of Promises, it’s never completely certain that a rejection is unhandled - for example, a handler may be attached at a later point. For this reason, many Promise implementations provide a rejectionHandled event that essentially ‘rectifies’ an earlier unhandledRejection event, indicating that it was handled after all.

Because not all of these APIs are consistent, this module has to internally keep track of unhandled promises that it has encountered. The problem is that this means it has to keep a reference to every Error that it encounters, which in turn will get in the way of the garbage collector - eventually creating a memory leak.

To prevent this, you can configure a timeout setting (defaulting to 60 seconds), after which the module will consider a rejection to have been ‘final’, so that it can remove it from its internal list, thereby freeing up memory. If a rejectionHandled for the error comes in after this timeout, it will be silently ignored.

Situations where it takes more than 60 seconds to attach a .catch handler are rare, but if you run into such a situation, you can increase the timeout value to accommodate that.



Returns a new emitter.

  • options:
    • timeout: Defaults to 60. The amount of time after which an unhandled rejection should be considered ‘final’. See the “Timeout” section above for more information.

emitter.on(“unhandledRejection”, callback)

Emitted whenever an unhandled rejection is encountered. The callback arguments are as follows:

  • error: The Error object (or other error value) that the rejection occurred with.
  • promise: The Promise for which the error occurred.

emitter.on(“rejectionHandled”, callback)

Emitted when a previously ‘unhandled’ rejection was handled after all (within the timeout). The callback arguments are as follows:

  • error: The Error object (or other error value) that the original rejection occurred with.
  • promise: The Promise for which the error originally occurred.