You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How often does it reproduce? Is there a required condition?
Always
What is the expected behavior?
There is some way to see the error in 'uncaughtExceptionMonitor', throwing inside of unhandledRejection converts the type to uncaughtException and loses context.
What do you see instead?
If you register unhandledRejection there is no way to get the default behavior of seeing it in uncaughtExceptionMonitor, it is completely prevented with no way to opt-out.
if unhandledRejection is registered it eats the exception and as a result no uncaught exception happens (uncaughtException is also not emitted).
I assume this is intended similar as uncaughtException actually eats the exception and process is not ended.
Maybe adding a never listener unhandledRejectionMonitor similar to uncaughtExceptionMonitor which just indicates the unhandled rejection without any side effect would be the way forward here?
@Flarna i'm fairly open to ideas, marking a rejection as to be reported seems fine. Right now throwing inside of unhandledRejection does this but also causes some other stuff to happen and loses fromPromise. I'm a bit skeptical of adding a new event for this though. At least for use cases I don't see a need to report unhandledRejections that are actually handled intentionally by the program, but there is no way to make them as unhandled when you use unhandledRejection events.
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.
Activity
Flarna commentedon Dec 18, 2021
if
unhandledRejectionis registered it eats the exception and as a result no uncaught exception happens (uncaughtExceptionis also not emitted).I assume this is intended similar as
uncaughtExceptionactually eats the exception and process is not ended.Maybe adding a never listener
unhandledRejectionMonitorsimilar touncaughtExceptionMonitorwhich just indicates the unhandled rejection without any side effect would be the way forward here?bmeck commentedon Dec 20, 2021
@Flarna i'm fairly open to ideas, marking a rejection as to be reported seems fine. Right now throwing inside of
unhandledRejectiondoes this but also causes some other stuff to happen and losesfromPromise. I'm a bit skeptical of adding a new event for this though. At least for use cases I don't see a need to report unhandledRejections that are actually handled intentionally by the program, but there is no way to make them as unhandled when you useunhandledRejectionevents.github-actions commentedon Jun 25, 2026
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
github-actions commentedon Jul 26, 2026
This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.