Hacker News Reader

A final .catch().then() swallows the error, .always() does not.

Catch "swallows" errors by design. Unless you re throw. chaining another then has no effect on the behavior of a previous catch.

Right, but in the context of the OP's question you'd need the second .then() to mirror what .always() is doing.

The point is, there is no way to do .catch().then() and throw the error unless you do some hideous type checking hack cludge. Hence the need for .always().

Yea, the `catch` would probably have to set an 'errors' object on the response. The following `then` would then decide whether or not to throw an error based on that. Not pretty.

Also, I think `finally` makes your code easier to read. I always put the same kind of cleanup logic in there, everyone on the team knows what to expect in that block.

If you rethrow in the catch the next then won't get executed.

Will finally be executed between the throw and whatever catches it or after?

If you are returning that promise, you'll need to handle both then and catch so the caller can chain their own catch.