doubling down on trpc

safe bet?

@joelhooks what are the alternatives?

@andrewingram good question!

bespoke api, similar to next-auth (we have this in play already) that works pretty well

creating individual api routes

serverful api (graphql, rest)

???

@joelhooks Never seen the appeal of trpc, GraphQL is just way better. The point of an API is that the technology on either side doesn't matter, but trpc locks you into JS on both sides.

Unfortunately there are many wrong ways to do GraphQL. The best implementations build on top of statically typed languages, like TypeGraphQL, async-graphql or my very own graphql-crystal.

@jgillich I've used graphql (well) quite a lot and it's dead to me
@joelhooks I feel like I’m going to give the most developer answer. It depends. It seems like a good solution to a tightly integrated Frontend and backend but it depends on the the scenario, team and technology.