Not getting legacy router ops in merged tRPC 9 router
Followed the guide to merge my large tRPC 9 router with tRPC 10, but now I can't use useQuery or access my old routers off of
trpc.
. I can see trpc.greeting
, though.
Even if I omit the MeasurementRouter.build()
TRPC router, or merge a basic router, the client still doesn't recognize my legacy procedures.
Not sure what to do here, have been hacking on this upgrade for a while and would greatly appreciate a push in the right direction.![](https://answer-overflow-discord-attachments.s3.amazonaws.com/1115768658459897856/Screen_Shot_2023-06-06_at_6.20.50_PM.png)
![](https://answer-overflow-discord-attachments.s3.amazonaws.com/1115768658778660925/Screen_Shot_2023-06-06_at_6.20.55_PM.png)
![](https://answer-overflow-discord-attachments.s3.amazonaws.com/1115768659101618266/Screen_Shot_2023-06-06_at_6.21.28_PM.png)
4 Replies
https://github.com/trpc/trpc/tree/main/examples/.interop/next-prisma-starter might give you hints?
GitHub
trpc/examples/.interop/next-prisma-starter at main · trpc/trpc
🧙♀️ Move Fast and Break Nothing. End-to-end typesafe APIs made easy. - trpc/examples/.interop/next-prisma-starter at main · trpc/trpc
I’ve copied the components/style in this one and that is how I got to this point, are there any examples with merged legacy routers?
Migrate from v9 to v10 | tRPC
Welcome to tRPC v10! We're excited to bring you a new major version to continue the journey towards perfect end-to-end type safety with excellent DX.
Yeah that isn’t an example project, that is documentation I’ve already been following. Thanks anyway