Is this library maintained?

[yumauri]

Hello!

I've found this library when I searched for tools for Algebraic Data Types in TypeScript, and was immediately impressed from documentation! Looks like the best library for ADTs I've seen so far. Looks awesome 🔥

I was a bit downcasted that documentation states, that it is for upcoming version 3, which is not ready yet.

Then I've checked NPM and saw, that release version 2.1.0 was published 4 years ago, and version 3 is still in development, with latest publish 6 months ago.

6 months ago is not so far in the past, my own library's latest version is the same age, and I perfectly understand, that sometimes there are not enough strength/motivation/desires/mental and physical health/name it, to work on a pet project. It is fine.

I just wanted to ask, is this library still in development and release of version 3 is still in plans? If yes, do you have some kind of roadmap, what should yet to be done for the release? I saw issue #17, but last message in it was two years ago. Also, do you think it is fine to use version 3.0.0-dev.27 in production, or you suggest agains it, maybe because of some unresolved undocumented issues?

[paarthenon]

Hello @yumauri !

Thank you for your interest in the project. I appreciate your kind words and I hope I can help provide some context.

In short yes the project is maintained. There are some updates on my mind actually. There's plenty of motivation, but I'm limited by some sincere personal challenges. The release of 3.0 is still on the table though I acknowledge I am a bottleneck at the moment and a more explicit roadmap would help ;)

do you think it is fine to use version 3.0.0-dev.27 in production

As a project maintainer talking to a fellow pro developer, I can't yet recommend it in production. It has not been battle tested to the degree I would like and the API is unstable. Functionality may be changed or removed between versions. There are some features not yet documented.

However as a casual coder talking to another open source contributor or someone working on a side-project, I've built projects that use [email protected].__ and it's been fine. I am waiting until the alpha release (with docs) to officially start recommending 3.0 as the preferred option, but I use it for my new projects and will provide help to other users who are open to doing the same. I feel it is the better developer experience. The caveat is it is still development software, so API changes may happen between versions and you may need to check my notes on GitHub when updating.

I hope that helps, and I hope you'll consider trying 3.0. Your feedback would help us get across the finish line.

[yumauri]

Thank you, I got it!
I think I'll give it a try (version 3 I mean) 👍