The inferred type of 'trpc' cannot be named without a reference
api
package (copied from https://github.com/t3-oss/create-t3-turbo/tree/main/packages/api) and a server + expo packages similarly copied from that monorepo.
Any ideas what I should be looking at to solve this issue?...how to solve this
is it possible to set a response middleware on Vanilla trpc client?
What's the best practices around tRPC to negotiate API-versions?
Is there a way to pass context or cookies to the client provider?
Is there a way to pass context or cookies to the client provider?
Why deprecate experimental_standaloneMiddleware?
shared useTRPCClient hook conversion to v11
Question: Is there a way to have a base interface for Trpc router?
persistedQueries & indexedDb
Public and Private procedures Not working with Clerk and Prisma
Properly handle unifying interfaces from tRPC call?
quests
and tasks
, which share several common properties, however they are named slightly differently (e.g. quests.startingAssessmentContent
and tasks.startingContent
), as well as a component which reads the contents of either one of these objects interchangeably.
I want to unify my interfaces for the tRPC procedure outputs for these two objects, so I made a custom hook:
```Typescript...Type 'QueryClient' is missing the following properties from type 'QueryClient': queryCache, mutation
Type 'QueryClient' is missing the following properties from type 'QueryClient': queryCache, mutationCache, logger, defaultOptions, and 4 more.ts(2740) context.d.ts(48, 5): The expected type comes from property 'queryClient' which is declared here on type 'IntrinsicAttributes & TRPCProviderProps<CreateRouterInner<RootConfig<{ ctx: object; meta: object; errorShape: DefaultErrorShape; transformer: DefaultDataTransformer; }>, { ...; }>, unknown>'...
@tanstack/query@4
How to properly handle Prima selects/includes with tRPC?
getById
to take a list that allows all possible attributes from the prisma models and optionally a list of models to include.
Currently, I define a list of all attributes on a global level for each router, that includes all includable Fields (I'd then do the same for the selectable fields). But that - even with just the includable fields - ends in this madness:
...onSuccess with createTRPCProxyClient
trpcNext from client for testing
Missing content type header for mutations leads to 405
Is there any way to temporarily disable mutations?
After upgrading to 11.0.0-next-beta.300, every request throws zod error
{"issues":[{"code":"invalid_type","expected":"object","received":"undefined","path":[],"message":"Required"}],"name":"ZodError"}
{"issues":[{"code":"invalid_type","expected":"object","received":"undefined","path":[],"message":"Required"}],"name":"ZodError"}
Setting up tRPC for next.js with edge AND serverless functions