NAre you reusing routers in multiple different APIs?
NThat sounds like a case for a dedicated package which contains common routers
NMmm that's a good point, you'd have to move your basic trpc setup down into a 3rd package which both common routers and API apps can consume
NWhich might actually be a good thing by the way, sharing a common Context/Meta type and base procedures/middlewares among APIs through a package
NCould you give an example? I'm reasonably sure you just need to break up one of the files a little more
NSure 
NCircular references are tough to unwrap, and tRPC is weird in that you have to actually do it! it's the reason why the setup guides suggest the files structure that they do (appRouter.ts, trpc.ts, routers) because routers and appRouter both depend on trpc.ts and appRouter depends on routers.