why moved from tRPC?

[dcsan]

i liked the stack you built before with tRPC, this seems like a step backwards? the endpoints can be typed but its all manual, and not enforced...

[matthew-sessions]

Since this project uses a framework Tanstack Start I use server functions as it ships the framework. If you prefer TRPC over server functions (they have the same core features tbh, just less setup than trpc) you can add trpc easily. Just create an API route at path /trpc and add a trpc handler.

You will just have to be aware of what code runs on the server vs on the client. Tanstack Start server functions can run on both the server and client without much consideration by you as the developer. With TRPC you may have issues with server side calls unless you configure your trpc client to have an explicit url.

[dcsan]

thanks for the response!
afaict you still need to explicitly setup return types from tanstack router function calls? eg declare types and create shared interface/type files, where tRPC gives you instant feedback and intellisense if you changed something? maybe i'm missing something in the setup, but that's the beauty of tRPC, just works instantly in realtime. even if there's a bit more setup.

i was not a fan of nextJS actions, they seemed to require a very limited subset of functionality eg you couldn't use classes easily, had to all just be async functions. and on top of that you're never sure where they're running without lots of use X directives... the slippery slope to RSC they were greasing to try and lock you in to their over priced hosting.

[matthew-sessions]

ed

sorry for the late reply. You don't need to declare the return type of a server function. It should just be inferred. The experience is very similar. I think server functions are easier to get setup with start (no need to do any type of integration). Trpc has query options which where built for tanstack query which is better than start. It is kind of funny that TRPC has a better integration with tanstack query than tanstack start server functions right now (I am sure start will roll features around this though)

Start function have really awesome isomorphic capabilities which work very well with the lifecycle the lifecycle of tanstack router.

My mental model here is:

1. Want to use the entire framework (tanstack start)? - Just use server functions
2. Want to build a SPA with no SSR? - tanstack router, query + TRPC