`useSuspenseQuery` returns unexpected `.json` and `.metadata` (SuperJSON)
trpc+solidjs
Best way to wrap procedure for error handling
withErrorHandling that you wrap all your procedures with? ...procedures on routers are typed any

Inferring Types not working as expected
Error: Switched to client rendering because the server rendering errored: UNAUTHORIZED

Max number of subscriptions
TRPCError: Unsupported GET-request to mutation procedure at path
TRPCError: Unsupported GET-request to mutation procedure at path "app.trackMetric"
...Context and TanStack
TRPC 11 Classic React Query custom hook
signup/signin
Pre-rendering Error with TRPC useSuspenseQuery â "fetch failed" During Build
Greeting component. Since the component uses useSuspenseQuery to call a TRPC endpoint, pre-rendering triggers the call and results in a "fetch failed" error because the route isnât available during build time. Known workaroundsâswitching to useQuery or using prefetch on the page componentâprevent the error; however, these solutions are not acceptable in this case.
Code Samples...Throwing error in trpc route, continuously sending a request
protectedProcedure on hello router to see if the Suspense and ErrorBoundary is working.
As you can see on my network tab I already have a thousands request, I followed the Tanstack React Query/Server Components .
And for the other screenshot that I provided, those are the only changes I made....
Error using prefetch query with TanStack Query
A query that was dehydrated as pending ended up rejecting. [[["tradeList"],{"type":"query"}]]: TypeError: (0 , __TURBOPACK__imported__module__$5b$project$5d2f$node_modules$2f2e$pnpm$2f$next$40$15$2e$3$2e$0_react$2d$dom$40$19$2e$1$2e$0_react$40$19$2e$1$2e$0_$5f$react$40$19$2e$1$2e$0$2f$node_modules$2f$next$2f$dist$2f$server$2f$route$2d$modules$2f$app$2d$page$2f$vendored$2f$rsc$2f$react$2e$js__$5b$app$2d$rsc$5d$__$28$ecmascript$29$__.createContext) is not a function; The error will be redacted in production builds
⨯ [Error: redacted] { digest: '2062921512' }
A query that was dehydrated as pending ended up rejecting. [[["tradeList"],{"type":"query"}]]: TypeError: (0 , __TURBOPACK__imported__module__$5b$project$5d2f$node_modules$2f2e$pnpm$2f$next$40$15$2e$3$2e$0_react$2d$dom$40$19$2e$1$2e$0_react$40$19$2e$1$2e$0_$5f$react$40$19$2e$1$2e$0$2f$node_modules$2f$next$2f$dist$2f$server$2f$route$2d$modules$2f$app$2d$page$2f$vendored$2f$rsc$2f$react$2e$js__$5b$app$2d$rsc$5d$__$28$ecmascript$29$__.createContext) is not a function; The error will be redacted in production builds
⨯ [Error: redacted] { digest: '2062921512' }
CreateCaller for router with AWS Adapters

Wrong type for results
Date type, however when queried with TanStack they are being returned as string. Is there a way to cast them to Date again?Query invalidation per mutation-key
Blob as response tRPC v.11
@trpc/server/adapters/express
Thanks!...How can I access the session in fastify when using `useWSS: true`?