comparison to trpc
n1ru4l opened this issue · comments
Especially for the server, we should have a comparison that shows the strengths and drawbacks of using feTS instead of tRPC.
@n1ru4l For me, it is a great way to validate request and response, but rewrite whole thing to native fetch at the end to reduce the bundle size.
Basically for me it is only dev dependency. I have met some issues with building gatsby.js project with feTS, but rewriting it to fetch fixes issues.
Wanted to +1 this. Took me a long time to find out about feTS. I was looking for a way to make OpenAPI compliant APIs and looked into hono with openapi middleware, trpc-openapi etc, but feTS is the most lightweight, integrated solution I've found so far :) The only drawback is using TypeBox instead of Zod but i understand why it is necessary! I wish you great success :)