neverthrow · Issues· 83 open

You don't need the isOk()/isErr() methods if you use discriminating readonly properties instead

Maintenance status

asyncAndThrough is implemented on Ok/Err but missing from IResult interface

ResultAsync missing _unsafeUnwrap() and _unsafeUnwrapErr() test utilities

[PROPOSAL] Do + bind / let for Result and ResultAsync

isErr() + early return limitations

Working with loops

Result.combine() with Result<void, E>[] is typed as Result<void[], E>, which when explicitly typed is incompatible with @typescript-eslint/no-invalid-void-type

Early return / short circuit pattern

Mentioned `safeTry` Error Inference Limitations in Docs

[BUG] ResultAsync.fromPromise fails with React 19 server components' Promise transmission

[Feature Request] make `fromPromise` second argument `errorFn` optional

Cannot preserve error types in nested function calls

[FEATURE REQUEST] ResultAsync.any feature request

Type inference error when using .andThrough()