tRPC, NextJS 14, createTRPCProxyClient, How can I globally manage errors?
next 14 setup error
No typesafety after migrating to 11?
t
is any...
is there a way to send a streaming response
Error: Tried to access "$types.__endpoint" which is not available at runtime
Error: Tried to access "$types.__endpoint" which is not available at runtime
at [blah]/functions/node_modules/@trpc/core/dist/index.js:344:23
...trpc output dates are typed as strings and not dates
TRPC v10 to v11 - change logs location
tRPC won't return route with function, only JSON

tRPC router won't return, unless it's just json.
How to make trpc output return strings and not dates
Cannot read properties of undefined (reading 'input')
Extending the client with "virtual" procedures
Dynamic Server Usage Error from RSC calls

Node 20, NPM: Send form values to DB with tRPC?

Getting type error in v11 when trying to instantiate createTRPCQueryUtils
Type 'CreateTRPCReactBase<CreateRouterInner<RootConfig<{ ctx: object; meta: object; errorShape: DefaultErrorShape; transformer: DefaultDataTransformer; }>, { allProjects: QueryProcedure<...>; project: QueryProcedure<...>; }>, unknown> & DecoratedProcedureRecord<...>' is not assignable to type '"The property 'query' in your router collides with a built-in method, rename this router or procedure on your backend." | "The property 'mutation' in your router collides with a built-in method, rename this router or procedure on your backend." | ... 6 more ... | TRPCUntypedClient<...>'.ts(2322)
createUtilityFunctions.d.ts(10, 5): The expected type comes from property 'client' which is declared here on type 'CreateQueryUtilsOptions<AnyRouter>'
Type 'CreateTRPCReactBase<CreateRouterInner<RootConfig<{ ctx: object; meta: object; errorShape: DefaultErrorShape; transformer: DefaultDataTransformer; }>, { allProjects: QueryProcedure<...>; project: QueryProcedure<...>; }>, unknown> & DecoratedProcedureRecord<...>' is not assignable to type '"The property 'query' in your router collides with a built-in method, rename this router or procedure on your backend." | "The property 'mutation' in your router collides with a built-in method, rename this router or procedure on your backend." | ... 6 more ... | TRPCUntypedClient<...>'.ts(2322)
createUtilityFunctions.d.ts(10, 5): The expected type comes from property 'client' which is declared here on type 'CreateQueryUtilsOptions<AnyRouter>'

LoggerLink logging only via server logger in prod
Better error tracing when using TRPC routers

client side Validation with ZOD
We're having some serious Intellisense performance issues with v10
mergeRouters
(we're working on changing this to a namespaced router) but we're having some serious performance issues (10s+ to open Intellisense in VSCode with extensions disabled). We've also confirmed that TypeScript gets slower the more routers we add.
Obviously this is expected, but we didn't think we'd run into this issue with 100+ procedures. We thought we'd be facing an issue like this with 2,000+. Any help on this would be appreciated. We'd be happy to send over an NDA and pay for help as well. Although I can always talk through what's going on here on Discord and add some traces if you feel it would be useful.
Btw this is in a monorepo configuration. I haven't yet tried isolating the package on its own and testing to see if the performance is any better. It's a very big project that powers our startup. Thanks....Parsing FormData on trpc