feat: Ability to merge routers with different contexts
Describe the feature you'd like to request
The ability to merge routers that have different contexts into one client. For example a Fastify tRPC server + a Next.js tRPC server that have different purposes, but both need to be consumed by the Next.js app which is not possible at the moment.
Describe the solution you'd like to see
KATT mentioned that really only error formatting needs to be the same, so some new merge routers method that merges any two routers as long as their error formatting is the same.
Describe alternate solutions
The only workaround I can think of off the top of my head is calling the secondary server (in my example, the Fastify server) with createServerSideHelpers and then proxying it with a new router inside the Next.js server, although this adds unneeded latency and complexity.
Additional information
https://github.com/trpc/trpc/discussions/5111
👨👧👦 Contributing
- 🙋♂️ Yes, I'd be down to file a PR implementing this feature!
How does funding with Polar work?
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too