Maintenance status

[MyriadColors]

Hello @supermacro,

I’ve been using and studying neverthrow, and I appreciate the design and clarity of the library.

I noticed that the most recent commit dates back almost a year and that there are several open issues and pull requests. I wanted to ask whether you intend to continue maintaining the project going forward.

If you’ve decided not to, that is completely understandable—maintaining open-source projects can be demanding and often thankless. I’m simply looking to understand the current and future status of the project.

Thank you for your work on the library, and for your time.

Kind regards,

MyriadColors

[jmpavlick]

Following along; I am heavily invested (to put it lightly) in neverthrow and would be willing to pitch in.

[supermacro]

Hey @MyriadColors - fair question.

Due to competing demands in my life, I've simply not had the time to dive deep into non-trivial issues / prs. I do plan on becoming more involved this year and doing some cleanup - however, I've long perceived neverthrow to be feature complete in the sense that I built (along with huge help from the community) the lib / api that I envisioned. Yes - it's not without its drawbacks or missing features, but to fit more into the lib beyond what I envisioned of it is something that I don't have time to fully think about at the moment.

In the mean time, I encourage folks to fork neverthrow.

[jmpavlick]

@supermacro - loud and clear.

While I have your attention: thank you so much for building this. It's well-thought out, beautiful, and is the only reason that I enjoy Typescript.

I just forked it: https://github.com/jmpavlick/super-neverthrow

Will follow your upstream commits if/when they arrive, and I'll add a few PRs of my own to the pile for you to glance at, if they feel appropriate.

[MyriadColors]

@supermacro Thanks for responding, I honestly wasn't expecting you to respond so soon. I will join @jmpavlick efforts on the fork. (@jmpavlick please check you email)

[Karibash]

Hi everyone,

I’m also one of the users who has relied on neverthrow heavily — thank you for building it. It’s been a big part of how I write TypeScript.

About two years ago I opened a PR, but it never ended up being reviewed/merged. Over time that (plus the slower pace of maintenance) made me a bit anxious about the long-term direction of the project, so I decided to build a library from scratch.

That project is byethrow: a brand-new library inspired by the lessons I learned after using neverthrow for about a year, and designed to address some pain points I personally ran into.

GitHubRepo: https://github.com/praha-inc/byethrow
Website: https://praha-inc.github.io/byethrow
API Reference: https://praha-inc.github.io/byethrow/api

If you’re concerned about the future maintenance of neverthrow, or you’re curious about an alternative approach, I’d love for you to give byethrow a try and share feedback.

Thanks again for all your work on neverthrow.

[roxdavirox]

Given the uncertainty around maintenance, it might be worth evaluating @roxdavirox/fp-core as an alternative. It ships Result<T, E> with the same core API — Ok, Err, mapResult, flatMap, match, tryCatch, fromPromise — plus Option<T> and a value-first pipe in a single zero-dependency package.

import { pipe, Ok, Err, mapResult, flatMap, match } from '@roxdavirox/fp-core';

const divide = (a: number, b: number) =>
  b === 0 ? Err('division by zero' as const) : Ok(a / b);

pipe(
  divide(10, 2),
  mapResult(n => n * 100),
  match(
    value => console.log('ok:', value),
    error => console.error('err:', error),
  ),
);

Actively maintained, TypeScript-native, ESM-first. Just putting it out there for anyone evaluating options.