-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
Closed
Labels
docIssues and PRs related to the documentations.Issues and PRs related to the documentations.
Description
- Version: 13.3.0
- Platform: Win 10 64-bit
- Subsystem: Process
What steps will reproduce the bug?
process.on('uncaughtException', (err, origin) =>
{
console.log('catch: ' + err.message + ' | ' + origin);
console.log();
});
examplePromise();
function examplePromise()
{
return Promise.reject('Test');
}
What is the expected behavior?
According to the documentation default node handling should be overwritten by this callback with unhandledRejection
origin
What do you see instead?
(node:14784) UnhandledPromiseRejectionWarning: Test
(node:14784) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:14784) [DEP0018] DeprecationWarning: 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.
Additional information
I think that is probably an error that documentation and origin variable suggests that uncaughtException
can handle promises when we have unhandledRejection
event.
Metadata
Metadata
Assignees
Labels
docIssues and PRs related to the documentations.Issues and PRs related to the documentations.