Show HN: TypeAPI – An OpenAPI alternative optimized for code generation (opens in new tab)

So why would I chose this? How do I even implement it on the server? There's a lot of talk about client libraries, even with OpenAPI as an output format (nice!), but what about the server side?

The JSON[2] module for REST looks similarly impressive, but I haven’t personally used it.

1. https://github.com/manifold-systems/manifold/tree/master/man...

2. https://github.com/manifold-systems/manifold/tree/master/man...

Aren't there enough tools already for OpenAPI to do this?

1 - https://smithy.io/2.0/index.html

Contrary to this approach, we (https://WunderGraph.com) ingest one or more OpenAPI and GraphQL apis and combine them into a backend for frontend. We have code generators for all major frontend frameworks, like react, svelte, Vue, solid, astro, etc... These don't just make calling APIs type-safe but also handle authentication, etc...

The BFF approach allows us to securely inject API keys or add a middleware using Typescript.

I'm curious what people think of this approach. Our users don't usually integrate one or two APIs but rather 20 or more. I guess it would be quite expensive if you had to write a custom specification for each service.

Very disingenuous to compare this to an LLM, it has none of the advantages and fails to differentiate itself from many preceding peers.

My current way of achieving codegen sdk w openapi is using the readme/api sdk framework maker, if you have good specs it works pretty great.

Add tests to the sdk, and you're both testing your openapi implementation, docs, and sdk in one test