Why can I not throw inside a Promise.catch handler?

by

As others have explained, the “black hole” is because throwing inside a .catch continues the chain with a rejected promise, and you have no more catches, leading to an unterminated chain, which swallows errors (bad!)

Add one more catch to see what’s happening:

do1().then(do2).catch(function(err) {
    //console.log(err.stack); // This is the only way to see the stack
    throw err; // Where does this go?
}).catch(function(err) {
    console.log(err.stack); // It goes here!
});

A catch in the middle of a chain is useful when you want the chain to proceed in spite of a failed step, but a re-throw is useful to continue failing after doing things like logging of information or cleanup steps, perhaps even altering which error is thrown.

Trick

To make the error show up as an error in the web console, as you originally intended, I use this trick:

.catch(function(err) { setTimeout(function() { throw err; }); });

Even the line numbers survive, so the link in web console takes me straight to the file and line where the (original) error happened.

Why it works

Any exception in a function called as a promise fulfillment or rejection handler gets automatically converted to a rejection of the promise you’re supposed to return. The promise code that calls your function takes care of this.

A function called by setTimeout on the other hand, always runs from JavaScript stable state, i.e. it runs in a new cycle in the JavaScript event loop. Exceptions there aren’t caught by anything, and make it to the web console. Since err holds all the information about the error, including the original stack, file and line number, it still gets reported correctly.

More Related Contents:

  1. How to return many Promises and wait for them all before doing other stuff
  2. What are asynchronous functions in JavaScript? What is “async” and “await” in JavaScript?
  3. Promise.all is returning an array of undefined and resolves before being done
  4. async/await always returns promise
  5. How to turn this callback into a promise using async/await?
  6. How to dodge jQuery promises completely when chaining two async jQuery functions?
  7. Cancel a vanilla ECMAScript 6 Promise chain
  8. Asynchronous exception handling with bluebird promises
  9. What is the difference between JavaScript promises and async await?
  10. How to wait for a JavaScript Promise to resolve before resuming function?
  11. Should an async API ever throw synchronously?
  12. When is the body of a Promise executed?
  13. ES6 Promise.all() error handle – Is .settle() needed? [duplicate]
  14. How do I tell if an object is a Promise?
  15. How to use promise in forEach loop of array to populate an object
  16. ES6 Promises – something like async.each?
  17. using async await and .then together
  18. How to implement a pseudo blocking async queue in JS/TS?
  19. How to return from a Promise’s catch/then block?
  20. Why does the Promise constructor require a function that calls ‘resolve’ when complete, but ‘then’ does not – it returns a value instead?
  21. When would someone need to create a deferred?
  22. map() function with async/await
  23. How to extract data out of a Promise
  24. Javascript Asynchronous Exception Handling with node.js
  25. Produce a promise which depends on recursive promises
  26. When does async function actually return a pending promise?
  27. Properly batch nested promises in Node
  28. JavaScript asynchronous programming: promises vs generators
  29. What are the implications of the recursive joining of Promises in terms of Monads?
  30. When is the body of a Promise constructor callback executed?

Leave a Comment