PApaduc·Oct 31, 2025
For the typescript world, there is neverthrow[0] which offers a similar Result type.
[0]: https://github.com/supermacro/neverthrow
In Result is all I needsupermacro
neverthrow
TypeScript2021–2025
supermacro / neverthrow
neverthrow
Type-Safe Errors for JS & TypeScript
7Distinct people
7Mentions
0Explicit recommenders
7.8KGitHub stars
What to know before exploring
What it is
Type-Safe Errors for JS & TypeScript
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year7 dated mentions
Observed mentions: 2021-10-11 20:34:32 UTC to 2025-10-31 10:03:28 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 1 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 2 | 1 | 1 |
What Hacker News says
7 sourcesNeverthrow – Type-Safe Errors for JavaScript and TypeScript
2 points · Open discussionIn the JS/typescript world, neverthrow [1] may be the closest library for this. If anyone has good experience with something else, please reply. Not sure if neverthrow is the right choice after replacing all Errors in a 16k LOC engine library with it. It did added more "noise" to the code. Would a custom bespoke code/library add less noise? I'm not sure.
[1] https://github.com/supermacro/neverthrow
In Railway Oriented ProgrammingVery 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…
In Error Handling PatternsOn my team we use Rust-style Result/Option types for any unrecoverable exceptions.
https://github.com/supermacro/neverthrow
In Ask HN: What is the “proper” way to do error-handling in TypeScript?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.
In The gotcha of unhandled promise rejectionsNeverthrow – Type-Safe Errors for JavaScript and TypeScript
1 points · Open discussion