meow
meow•13mo ago

TRPC Vanilla Client (T3 stack)

I'm using the T3 stack (Next + TRPC + etc) and I'm trying to figure out how to do vanilla queries that don't come with the baggage of a hook. 
const hello = await api.example.hello.useQuery()
const hello = await api.example.hello.useQuery()
1 Reply
jkob_
jkob_•13mo ago
Hey - had the same issue and think I have figured out a solution. The useQuery options were all coming from createTRPCNext<AppRouter>. I think this creates the ability to get the frontend hooks but doesn't create the normal async await versions. If you create an additional object, a createTRPCProxyClient<AppRouter> I think that creates the async/await queries you might be looking for Don't work for trpc so might be wrong though.
More Posts
Multiple Inputs on TRPC Procedure?Essentially I'm trying to pass a cart (array of objects) into a public procedure (doing so fine). I adapter for hono or hattip?we’ve got adapters for express, stand alone node and next. I wonder how easy would it be to make adKeep getting 500 error response I can't figure outWith both queries and mutations I get back this response saying that there's html in the response antRPC & redux toolkit queryNode 18, pnpm, ts, vite, toolkit. Cant find any proper info how to use tRPC with toolkit query; If Ihow can I globally set a "middleware" callback for all onErrors on my React Query calls?this is a little specific but Im struggling on it Im using the TRPC server as a BFF for my backend Upgrading from tRPC v9 and NextJS v12. Should I upgrade NextJS first or tRPC?I have an app built from the tRPC + NextJS + Prisma starter, and I'd like to upgrade from tRPC v9 anprefetchinfinite not working when inputs are differentIve been trying to figure out why prefetching doesnt work when the inputs are different between preftRPC + App directory + SSR - current state?What is the current state of the technologies working together with or without SSR? It looks like so