Amir
Amir3mo ago

queries and mutations has wrong response type in client ( monorepo )

No description
No description
6 Replies
Amir
Amir3mo ago
anyone has this kinda experience ?
Amir
Amir3mo ago
its show correct in router side
No description
Amir
Amir3mo ago
but 'any' in client side
BeBoRE
BeBoRE3mo ago
Did you setup your typescript correctly with strict?
BeBoRE
BeBoRE3mo ago
FAQ / Troubleshooting | tRPC
Collection of frequently asked questions with ideas on how to troubleshoot & resolve them.
Amir
Amir3mo ago
thank you bro when you import a library like this in backend: @/lib/pocketbase its cant detect the types in frontend side typescript is very powerful and sometimes weird
More Posts
tRPC + React Query Data Invalidation?Hey y'all, I'm working with tRPC and React Query and just trying to understand how this works. I havtrpc optimistic updates causing data flickerI'm trying to add optimistic updates to a calendar component but when the mutate function is called > Error: Invariant: headers() expects to have requestAsyncStorage, none availableHi, I use trpc v1045.1 in next 14.1 app router. I call it server side and have the following. ```js How do I exclude properties while returning data?I basically need to create a dto's that would exclude properties like access keys etc. while returniDoes anyone have an example of subscriptions implemented in CloudFlare Workers?I'm trying to use subscriptions via WebSocket in CloudFlare Workers, but it's been a real pain so faTRPCClientError: Unable to transform response from serverI am currently encountering this error occasionally in my apps. I am using a Monorepo, which includeUnexpected tokenWorks fine locally, doesn't work when deployed to AWS via sst.dev. Was working last night. RedeployeContext is not being passed correctlyI will include my setup at the end. My problem is that I am using nextauth with database sessions anHow to get the Request Body data of QStashHello everyone. I'm currently working on a client project that involves using trpc with Next.js. We'Preventing uncaught error propagation from server to clientHello guys, is there any way to create default error handler? I want to avoid leaking internal infor