Why doesn’t the try catch block catch the promise exception?

by

I can see two possible aspects to your question:

  1. The error being thrown in test is in the synchronous (not asynchronous) part of test. Why is it a promise rejection rather than a synchronous exception?

  2. The promise from test() is being rejected, why doesn’t catch catch that rejection?

#1 – Why is it a rejection?

Because even if an async function throws during the synchronous portion of its work, that just rejects the promise it returns, it doesn’t raise a synchronous error. It’s just a design decision made during the design of async functions, and a smart one — if it were a synchronous error when throwing in the synchronous part of the function but a promise rejection after that, it would be chaotic and hard to understand. So it’s simple: throwing in an async function always rejects its promise.

(This is consistent with how the promise constructor treats the executor callback you pass into it. When you do new Promise((resolve, reject) => /*...*/}), the promise constructor calls your function synchronously, but if you throw during the call, it uses what you throw to reject the promise rather than allowing it to continue as a synchronous exception.)

#2 – Why isn’t rejection caught by the catch block?

Because you’re not using await. Promise rejections are only exceptions when you are awaiting the promise. If you use the promise methods then/catch/finally to attach handlers, rejection is handled by calling the rejection handler, not by the exception mechanism.

So either use promise methods to attach fulfillment and rejection handlers:

test()
.then(result => {
    // ...use `result` here...
})
.catch(error => {
    // ...handle/report error here...
});

Or use await in an async function (or at the top level of a module if you have top-level await in your enviroment):

// In an `async` function (or the top level of a module in cutting-edge environments)
try {
    const result = await test();
    // ...use `result` here...
}
catch(err){
    // ...handle/report error here...
}

More Related Contents:

  1. What is the explicit promise construction antipattern and how do I avoid it?
  2. How to return many Promises and wait for them all before doing other stuff
  3. What’s a good way to extend Error in JavaScript?
  4. Cancel a vanilla ECMAScript 6 Promise chain
  5. Why is my infinite loop blocking when it is in an async function? [duplicate]
  6. fetch: Reject promise with JSON error object
  7. How to check if an object is a Promise?
  8. What is the best way to limit concurrency when using ES6’s Promise.all()?
  9. What do double brackets mean in javascript and how to access them
  10. How do I create a custom Error in JavaScript?
  11. Catch all unhandled javascript promise rejections
  12. using a fetch inside another fetch in javascript
  13. How to measure the execution time of a promise?
  14. Why is the response object from JavaScript fetch API a promise?
  15. What is the difference between “event loop queue” and “job queue”?
  16. What are asynchronous functions in JavaScript? What is “async” and “await” in JavaScript?
  17. What is the intention behind clause 2.2.4 of Promise/A+ spec?
  18. ES6 promise execution order for returned values
  19. Promises, pass additional parameters to then chain
  20. What happens if you don’t resolve or reject a promise?
  21. Promise and Promise.all(array) executed before array fulfilled [duplicate]
  22. Node.js: When to use Promises vs Callbacks
  23. How can I export promise result?
  24. Are JavaScript forever-pending promises bad?
  25. ES6 Promise replacement of async.eachLimit / async.mapLimit
  26. Why does JavaScript Promise then handler run after other code?
  27. What are the implications of the recursive joining of Promises in terms of Monads?
  28. Promise.all is returning an array of undefined and resolves before being done
  29. Weird behavior with Promise throwing “Unhandled promise rejection” error
  30. Promise.resolve().then vs setImmediate vs nextTick

Leave a Comment