T
tRPC
Issues with subrouters being treated as any on client
Issues with subrouters being treated as any on client
I have 3 sub routers, all with a hello query just returning an object with world. I'm using nextjs with version 10.32.0 on both client and server (server is in separate express application) and the inferred types aren't working - it's treating the subrouter as an "any" type in the client, but the result works correctly when logged to the browser. We've setup everything we believe correctly with a nextjs frontend and an express backend. We're using pnpm workspaces, has anyone seen an issue like this before? TS and all versions are exactly the same.
Looking for more? Join the community!
T
tRPC
Issues with subrouters being treated as any on client
T
tRPC
Issues with subrouters being treated as any on client
Recommended Posts
tRPC + Express + Open TelemetryI'm wondering if anyone has experience using tRPC in conjunction with Express and Open Telemetry. I'Strange trpc typesHello, I just installed a fresh `trpc` project with `prisma` and `next`.
I have a prisma schema suchIs there a version of tRPC v10 that works with Next 12?Hi,
is there a version of tRPC that works with Next 12 and React 17? We want to incrementally adoptRunning TRPC on Vercel with custom serialization failsHi all,
I'm having some difficulties with the serialization of my objects when I run on vercel.
I'm