Will TypeStyle be maintained?

[natorojr]

Hello @basarat

I would like to know if this project will continue to be actively maintained. I am considering it for a Production project, but I have not seen any commits in over a year and there are many open issues.

This is a great project! I very much appreciate your work on TypeStyle and, in general, your contributions to open source.

If you need help maintaining this project, I can offer a few hours per week of my time. I have 20+ years of experience in software engineering and JavaScript (though only 3 years with TypeScript).

Alternatively, my company can sponsor this project and offer you a yearly stipend to ensure the project continues being maintained while we’re using it in Production.

Please let me know.

Thank you!

[basarat]

That is very generous. As far as I am concerned it works fine for me. I've sort of taken a break from open source and focusing more on video training content.

@notoriousb1t is the other owner if he wants to chime in. I'm out 🌹

[natorojr]

Thanks for your reply @basarat -- I saw your TypeStyles video on Egghead and it was very helpful. Best of luck with generating more training content.

@notoriousb1t If you need help maintain the TypeStyles project, please let me know. Since I'll be using this in a production app, I mostly just want to make sure that (1) 3rd-party dependencies (package.json) keep getting updated and (2) bugs are being addressed.

Best!

[notoriousb1t]

Admittedly, I have kind of checked out from open source the last few years (which is my personal response to burnout), but I am thinking of becoming more engaged in a smaller capacity.

I would be happy to have another maintainer, but I think there are some important guidelines that should be continued:

1. Maintain backward compatibility as much as possible
   The fact that we have only around 20 issues and so many downloads is a good indicator that the way the library works in general is good and doesn't need to be revisited. Any new features must be evolutions and we should have really good reasons to make breaking changes and introducing new concepts. We can always add more libraries, but I think we should keep TypeStyle itself very stable

2. Avoid taking on more dependencies
   I think the two runtime dependencies are good. We need to keep the library as small as possible

Both of these have to do with stability, which is incredibly important for users.

Regarding compensation, I think maybe there is a third option here. If your company is willing to set aside about 4 hours of engineering time per month for updating deps and solving bugs, we could add their logo somewhere as a "sponsor" as long as that agreement is kept. I would never ask someone to do free work for their current employer 😄

[satvikpendem]

Hi @notoriousb1t, I'd be willing to help keep the library maintained, I use it in production as well and would love to help out. Let's talk more.