Is Typesaurus no longer maintained? (It is and you can hire me to make Typesaurus better for you)

[NixBiks]

Hello,

Just came across this library and it looks pretty awesome and great documentation too. It's feature rich which is usually good but it also seems the library is no longer maintained which is restricting me from adopting it.

Is it the plan to continue maintaining though?

[lixb-v]

I feel the same way.

[Moe03]

yea we need to use it as well, prob will fork it to allow more configurations, vector db support in firestore also is needed in this lib, anyone wants to help?

[kossnocorp]

Thank you for the kind words. I put hundreds of hours into it during the last five years, and I am glad you recognize how good it is.

I understand that in the modern world, it is expected that open source gets frequent updates even though it does not necessarily correlate with the quality and usefulness of a project. It makes me sad that despite all the hard work, it is not enough unless I continue and do it often.

The truth is that every open source plateaus at some point due to shifted focus, the natural ceiling of what can be done, and lack of time.

I'm in a position where it satisfies my production needs, but it is hard to find external motivation to advance it. It is very niche, with a small user base and sparse feedback.

I tried to seek the support of the Google/Firebase team, and even though they were nice, it ended nowhere. I couldn't even make them publish a blog post or retweet my announcement. I got the impression that they don't think Firestore has a type-safety problem and are unwilling to engage. We see the issue differently. I had to cover many edge cases to make working with Firestore type-safe, and it's evident to me that there's a big problem. I don't think it will ever change, and I will get any support from Google.

Now, I have a few options:

1. Let it die. I don't like hundreds of hours of hard work going to waste, so it's a bad option for me.
2. Let someone else continue to work on it. This will result in a decline in quality and, sooner or later, the same situation, but worse. It is practically the same as 1.
3. Find a few hours a week/month and work on whatever people report in GH issues. This is unsustainable and also just a slow death.
4. Partner with companies that find it helpful and do consulting work for them, building features they need, fixing bugs they have, and helping to get the most out of it.

I think only option 4 leads to a place where the project is sustained, its users are confident that any problems are going to be solved, needed features are going to be built, and I consistently find time to work on it as it brings food to the table.

So here's my proposal @NixBiks @lixb-v and whoever reads it: if you're serious about using Typesaurus in your product, hire me at an hourly rate. I will be responsive and make any requests happen.

Companies that value the same things as me will immensely benefit from Typesaurus, and with my involvement, it will be smooth sailing.

Email me at koss@nocorp.me, and we will discuss the details.

Now, Typesaurus continues to live, and I will continue to work on it slowly, improving it and solving critical issues on my own terms.

So, answering the issue title, Typesaurus is still maintained.