Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

comparison to trpc #679

Open
n1ru4l opened this issue Oct 16, 2023 · 2 comments
Open

comparison to trpc #679

n1ru4l opened this issue Oct 16, 2023 · 2 comments

Comments

@n1ru4l
Copy link
Collaborator

n1ru4l commented Oct 16, 2023

Especially for the server, we should have a comparison that shows the strengths and drawbacks of using feTS instead of tRPC.

@JustFly1984
Copy link

@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.

@sarimabbas
Copy link

sarimabbas commented Oct 28, 2023

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 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants