Yeah I agree that it is impossible to know exactly what the fields are without a real documented source, but I figured this could be a decent option when there are no other alternatives available. While it's not perfect, it can provide a starting point for creating types based on sample data, which can then be refined as you work with the API and gain more understanding.
Tbh, there is no benefit of using this package if the API you are working with has an openapi spec, as there are other great libraries to help you generate accurate types such as https://github.com/openapi-ts/openapi-typescript. But I made this package to use when working with external apis that don't have an available spec.
I had a look at this, but the setup seems like it's for automated emails. I'm mainly looking to be able to personally send from the custom email without ending up in spam...
I think the obvious answer right now is anything related to AI. But I'm actually quite excited about the embrace of open-source applications that traditionally have not been, such as Cal.com and Mattermost.
We use monorepos in my company too, but we use one for each product, and it works really well for that. But for the whole company to be in a single monorepo just seems like it would require a lot of effort to maintain.