-
Notifications
You must be signed in to change notification settings - Fork 312
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
What adapters should we add next? #356
Comments
I took a look at hono. It is based on Web Standard API, so I guess we don't need extra adapter. Probably, new example is enough |
We could maybe just have a section in docs of code-snippets how you can use the standard server handler for different setups, similar to https://trpc.io/docs/server/adapters/fetch#runtimes-specific-setup |
Yeah, sounds reasonable |
I'm going to take a look at Elysia during the day. Let me know, if it's already in progress on your side |
@juliusmarminge Created PR with new doc page and pair of new examples #364 |
React Native would be nice. Especially if I can share Uploadthing code between React Native (Expo w/ Expo Router etc.) and Next.js. |
See #583 |
Remix! |
Phoenix would be great! |
In
[email protected]
, we shipped two new backend adapters, Express and Fastify. What other adapters should we add?Also keep in mind the base
server
handler can be used for any server using web standard Request/Response. Some examples of runtimes/frameworks that is (should) already be supported using this adapter areThe text was updated successfully, but these errors were encountered: