WorkerGlobalScope: unhandledrejection event

The unhandledrejection event is sent to the global scope (typically WorkerGlobalScope) of a script when a Promise that has no rejection handler is rejected.

This is useful for debugging and for providing fallback error handling for unexpected situations.

Syntax

Use the event name in methods like addEventListener(), or set an event handler property.

js
self.addEventListener("unhandledrejection", (event) => {});
self.onunhandledrejection = (event) => {};

Event type

Event properties

PromiseRejectionEvent.promise Read only

The JavaScript Promise that was rejected.

PromiseRejectionEvent.reason Read only

A value or Object indicating why the promise was rejected, as passed to Promise.reject().

Examples

Basic error logging

This example logs information about the unhandled promise rejection to the console.

js
self.addEventListener("unhandledrejection", (event) => {
  console.warn(`UNHANDLED PROMISE REJECTION: ${event.reason}`);
});

You can also use the onunhandledrejection event handler property to set up the event listener:

js
self.onunhandledrejection = (event) => {
  console.warn(`UNHANDLED PROMISE REJECTION: ${event.reason}`);
};

Preventing default handling

Many environments (such as Node.js) report unhandled promise rejections to the console by default. You can prevent that from happening by adding a handler for unhandledrejection events that—in addition to any other tasks you wish to perform—calls preventDefault() to cancel the event, preventing it from bubbling up to be handled by the runtime's logging code. This works because unhandledrejection is cancelable.

js
self.addEventListener("unhandledrejection", (event) => {
  // code for handling the unhandled rejection
  // …

  // Prevent the default handling (such as outputting the
  // error to the console)

  event.preventDefault();
});

Specifications

No specification found

No specification data found for api.WorkerGlobalScope.unhandledrejection_event.
Check for problems with this page or contribute a missing spec_url to mdn/browser-compat-data. Also make sure the specification is included in w3c/browser-specs.

Browser compatibility

BCD tables only load in the browser

See also