Handle React error boundary
useErrorboundary
set to true and wrapped my component that uses trpc query with the React Error Boundary but it doesn't seem to be able to catch it. When I just throw before the query it successfully intercepts the error but from trpc seems its not doing that? Am I doing something wrong ??
```js
const [queryClient] = useState(...Any tips for Typescript slowness?
Change status of useMutation from 'success' back to 'idle'
Is it possible to call one procedure in another?
Handling Query Errors at Root of App (v9)
NextJS
frontend every time there is an error from useQuery
in a functional component. Is there a way to add something at the root of my app that can watch for trpc errors or do I have to handle it at every use of useQuery
? (note: i am on v9)tRPC Client webpack error
cookies, headers and authentication
res.cookie("name", "value")
for example.
alternatively I can do res.set"set-cookie", "name=value")
.
how can I do something one of the two above with trpc?
...remove query
trpc hook pattern. This works, but I’m not convinced…
Catch TRPCError, ZoddError on the front-end

implicitly has type 'any' because it does not have a type annotation and is referenced directly

Why do some examples create PrismaClient in context, and others don’t
AppRouter type any?

How to call TRPC procedures directly, without creating a router and calling createCaller?
someProcedure({input, ctx})
We frequently call TRPC procedures from within other TRPC procedures....correct way to call TRPC inside a function

Cannot find namespace 'trpc'

use tRPC for RPC calls instead of gRPC
tRPC caching vs Vercel dynamic edge caching
Ignore Errors from batch calls