McPizza
McPizza•11mo ago

Calling a tRPC service from another tRPC service

I have 2 services (App1 and Service2) App1 is client facing and uses trpc well But occasionally App1 backend needs to call a procedure on Service2 Should I just use the vanilla client on App1 backend and import types/context from Service2? p.s. this is not Next ecosystem
2 Replies
McPizza
McPizza•11mo ago
Ended up creating trpc client in the backend, importing and using it within App1 procedures Works ok, had some funkiness with fetch Good enough
sachin
sachin•11mo ago
yeah your solution sounds best
More Posts
charset=utf8 results in empty inputI'm using trpc-openapi and some of our customers are using Zapier to communicate with it. Zapier usIs there a way to alter the query key generated by trpc?I want to pass a boolean flag (`initial`) to the backend saying if it's a first call of a given procuseMutation throwing 500 errorsI've setup my next 13 app router project and started using some queries that worked fine, however thTRPC Nextjs App Router API Base URLIs there any issues with me placing trpc route handler in the root of my api folder? I don't really Turborepo, nextjs, vite react app, express serverI have following structure Apps: First Frontend - Nextjs app Second Frontend - Vite ReactApp BackenRouter/Middleware Chaining in V10Heyo, finally migrating from v9 to v10 after putting it off for a while. Is it just me, or is this mthrowing custom errors from mutationsany idea why trpc is ignoring the catch expression? it just throws its own error about unique consttrpc in a pnpm monorepoHi all 👋 I was wondering if there is a recommended setup for monorepos, in our case with pnpm workTS Error with React when creating client "useContext" collides ....when creating the client i get following error: The property 'useContext' in your router collides wType 'NextRequest' is missing properties from type 'NextApiRequest'Enviorment: Node 18, pnpm Hi, I'm facing an error, where in my app i get this error at `createTRPCC