How to wrap response type with useAsyncData from Nuxt?
useAsyncData(() => client.someProcedure.query())
on every call so that I don't double fetch during SSR. Is there a way to make a wrapper client that will wrap query and mutation responses with the useAsyncData()
call? I would love if the client was typed and I could call it the same way I can call the vanilla client.How to define per route staleTime on queryClient?
Can i use a single trpc proxy client in NextJS 12?
[Typescript] Client query/mutate has any type

Trpc V11 Nuxt 4
server side prefetch + optional client side refetch
[Help] Fastify session http only cookie differs
126 routers | TS7056: inferred type node exceeds - Multiple Providers?
How to get cursor in new Tanstack Query integration?
cursor
(or pageParam
) in the new infiniteQueryOptions
function? The current procedure input takes a cursor
but I'm getting and error saying cursor
is not passed to infiniteQueryOptions
, and I can't pass it manually as it is calculated using getNextPageParam
.monorepo can't resolve trpc context
Type error: Property 'Provider' does not exist on type '"The property 'useContext' in your router collides with a built-in method, rename this router or procedure on your backend." | "The property 'useUtils' in your router collides with a built-in method, rename this router or procedure on your backend." | "The property 'Provider' in your router collides with a built-in ...'.
Does anyone have a decent idea or a suggested setup for express backend, nextjs front, and trpc 11? I want a mono so that I can share a lot betyween them + share hooks with future projects. I want express so that I can scale them in AWS. and next pushed through AWS amplify. That's the current idea ayways. This is my experimental project where the dev works but the build fails. This is killing me for over a week now.https://github.com/dsmurl/an-express-next...
Catch the error on trycatch and show the message
operation input is formdata but trpc makes it an application/json POST call
v11 with tanstack mutation not invalidate query

Extra query keys for functions for invalidation
Type 'DecorateQueryProcedure<{ input: string; output: { id: string; name: string; }; transformer: fa
Should `.queryFilter()` not take a partial arg?
.invalidate(partialObject)
to qc.invalidateQueries(trpc.path.queryFilter(partialObject))
doesn't work, since queryFilter
type isn't partialled. Is this correct behavior? I would imagine the filter could be anything
Really like this integration update btw π...skipToken combined with the new tanstack query options
different transformers for different routers
json
field in it, and TS types are mismatching (TS types assume no wrappers will be there)super quick question about prefetching
prefetch
to fetch data on the server to ensure that both queries are running at the same time? From the looks of it trpc handles this automatically so it is unneeded?
await Promise.all([api.guild.get.prefetch({ guildId }), api.application.getList.prefetch({ guildId })]);
await Promise.all([api.guild.get.prefetch({ guildId }), api.application.getList.prefetch({ guildId })]);
TRPC not writing to QueryCache?