Movatterモバイル変換


[0]ホーム

URL:


  1. Web
  2. Web APIs
  3. WorkerGlobalScope
  4. rejectionhandled

WorkerGlobalScope: rejectionhandled event

Baseline Widely available

This feature is well established and works across many devices and browser versions. It’s been available across browsers since ⁨July 2020⁩.

Note: This feature is only available inWeb Workers.

Therejectionhandled event is sent to the script's global scope (typicallyWorkerGlobalScope) whenever a rejectedPromise is handled late, i.e., when a handler is attached to the promise after its rejection had caused anunhandledrejection event.

This can be used in debugging and for general application resiliency, in tandem with theunhandledrejection event, which is sent when a promise is rejected but there is no handler for the rejection at the time.

Syntax

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

js
addEventListener("rejectionhandled", (event) => { })onrejectionhandled = (event) => { }

Event type

APromiseRejectionEvent. Inherits fromEvent.

Event PromiseRejectionEvent

Event properties

PromiseRejectionEvent.promiseRead only

ThePromise that was rejected.

PromiseRejectionEvent.reasonRead only

A value orObject indicating why the promise was rejected, as passed toPromise.reject().

Example

You can use therejectionhandled event to log promises that get rejected to the console, along with the reasons why they were rejected:

js
self.addEventListener("rejectionhandled", (event) => {  console.log(`Promise rejected; reason: ${event.reason}`);});

Specifications

Specification
HTML
# handler-workerglobalscope-onrejectionhandled

Browser compatibility

See also

Help improve MDN

Learn how to contribute

This page was last modified on byMDN contributors.


[8]ページ先頭

©2009-2025 Movatter.jp