ts-results
neverthrow
| ts-results | neverthrow | |
|---|---|---|
| 3 | 16 | |
| 10 | 2,447 | |
| - | - | |
| 0.0 | 5.8 | |
| over 1 year ago | 8 days ago | |
| TypeScript | TypeScript | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ts-results
- ts-results - a lightweight result wrapper to exhibit success/failure instead of using/throwing exceptions.
- ts-results - a lightweight typescript result wrapper to exhibit success/failure instead of using/throwing exceptions.
- ts-results - a lightweight type safe result wrapper to exhibit success/failure instead of using/throwing exceptions.
neverthrow
-
Error Handling Patterns
Very timely, was just trying to understand how to improve error handling with typescript recently and came across neverthrow (https://github.com/supermacro/neverthrow) which looks promising…
-
Ask HN: What is the “proper” way to do error-handling in TypeScript?
On my team we use Rust-style Result/Option types for any unrecoverable exceptions.
https://github.com/supermacro/neverthrow
-
The gotcha of unhandled promise rejections
I was happy when Promise became available, but in retrospect I'd wish we would have skipped ahead and gotten Observable (e.g: https://rxjs.dev/) instead to enable more powerful functionality and composition etc.
In Typescript dealing with rejection is also painful since rejection reasons can't be guaranteed to be Error even when you always take care of that. And it can't help you guarantee that you're handling all types of errors thrown. For that purpose I'm thinking of using https://github.com/supermacro/neverthrow#readme or https://swan-io.github.io/boxed.
-
How has learning Rust been a benefit to you in other programming areas?
I highly recommend the neverthrow library for bringing Result to Typescript.
-
functional error handling (functions return error) recommendations
I like the Result monad from here: https://github.com/supermacro/neverthrow
-
How to know if a function throws in Typescript?
What do you think of neverthrow?
-
ts-results - a lightweight result wrapper to exhibit success/failure instead of using/throwing exceptions.
I use https://github.com/supermacro/neverthrow for this
-
Handle Javascript errors like in Go
See neverthrow as an example of correctly encoding the failure into the return type of the function.
- Why doesn't typescript have a throws type to annotate functions that can throw an error?
-
what's the recommended way to handle error in TS?
I use Neverthrow. Same idea, concurrent projects...
What are some alternatives?
ts-results - A typescript implementation of Rust's Result object.
oxide.ts - Rust's Option<T> and Result<T, E>, implemented for TypeScript.
fp-ts - Functional programming in TypeScript
result - A TypeScript result type taking cues from Rust's Result and Haskell's Either types
functional-conditionals - A library for writing if / else if / else in a functional way.
eslint-plugin-promise - Enforce best practices for JavaScript promises
TypeScript - TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
dbg-expr - A helper for evalutating and logging an expression at the same time.
protonic-ui - React native UI Kit for mobile apps.
rustic_result - Result monad for Elixir inspired by Rust Result type
boxed - Essential building-blocks for functional & safe TypeScript code