Tried Hono + RPC, Hono + Zod/OpenApi and now Hono + tRpc. None so far have worked seamlessly to provide client side typings. Feels like just running some code gen on save (bit like flutters build_runner) to create static types for client usage will be most robust and versatile approach. Whilst I’ve been thinking moving over to a more rpc approach from Rest for a while now (what happens when you have 60+ serverless functions), wondering is jt the thing to do? And is tRpc the best solution ?
@code_coded orpc.unnoq.com is what you want Literally using it right now with arktype.io as the validator.
@code_coded I think rpc is the pinnacle of DX and that TS Go will make it viable for a lot of repos (maybe in combination with @arktypeio and other improvements in type performance)
@code_coded I found that it takes some time over all the trpc boilerplate in the beginning but once it's up a running it makes building/expanding a codebase so much quicker and easier. It's worth the investment.
@code_coded Better t stack with orpc and hono - flawless!