exceptionally VS ts-results

I one also thought that handlong errors works better when havung a good structure but that didn't really plan out. I stopped throwing anything inside my codebases. The only way to get full knowledge over the possible outcomes of a function call is if the function also returns exceptions instead of throwing them. TypeScript will not help you if something gets thrown. I wrote my own little library to handle this: https://github.com/ivanhofer/exceptionally I recently discovered that there are also other solutions out there that do something similar. With such an approach you will also know after 5 and more levels of function calls if your code really covers all possible outcomes. Really useful for refactoings!

For TypeScript developers, the ts-results library is a great tool to apply Rust's error handling pattern, simplifying the implementation of Rust’s `Result’ type in TypeScript.

Nicer way to go about this is `ts-results` which introduces the `Result` type, inspired by rust.

https://github.com/vultix/ts-results

I can't speak to it much myself as I don't have any experience with this pattern but I came across this the other day and your post made me think of it. https://github.com/vultix/ts-results Seems like it may not longer be maintained but might be worth comparing it your implementation. Allegedly the module 'fp-ts' also has this functionality but its another thing I have not looked into much.

https://github.com/vultix/ts-results for the former.

I've recently been a fan of the Rust style Result return types. There's a few projects doing this but I've been using ts-results.

This looks fantastic! I’ve been using the types from ts-results in a project for work and it’s been so nice, but I’ve been getting frustrated by the outdated documentation and lack of responses to PRs that have been opened. I was considering writing one of these libraries myself, but this looks like a perfect replacement!