What's the best way to debug the match results?

[ElasticBottle]

I have

export const getApiClient = createIsomorphicFn()
  .server(() => {
    const request = getRequest();
    const client = createRouterClient(router, {
        context: () => createApiContext(),
    })    
    return client;
  })
  .client(() => {
    const client = createORPCClient(createRpcLink({ baseUrl: window.location.origin, path: "/api/rpc" }));
    return client;
  });
export const getApiClientRq = () => createTanstackQueryUtils(getApiClient());

export const router = {
  project: lazy(() => import("./project")),
  campaign: lazy(() => import("./campaign")),
  campaigns: lazy(() => import("./campaign")),
};

Calling getApiClientRq().campaign.list will somehow trigger the project route, but calling the campaigns will be fine.

Not even sure how to create a repro/debug, I have other routes, but these are the only two that collide right now

Any ideas will be appreciated!

[dosubot[bot]]

The ORPC router matches routes by building a flat tree of HTTP paths, and lazy routes are only loaded when their prefix matches the incoming request. If two routes share similar prefixes or if the lazy import exports are misaligned, the matcher can pick the wrong route. In your case, this could explain why campaign triggers project—the matcher may be resolving the wrong lazy module or path due to how the tree is built and how the HTTP path is normalized.

To debug this, you can:

• Log the router tree and pending lazy routers by inspecting the StandardRPCMatcher instance (used internally by the handler). This will show you which paths are registered and which lazy routers are pending resolution.
• Use the unlazyRouter utility to fully resolve your router and inspect the actual structure and available routes at runtime. This can help you spot naming or export issues in your lazy modules.
• Check that your lazy imports (./project, ./campaign) export the expected router objects and that there are no naming collisions or default export mismatches.
• If you have middleware, ensure it isn't modifying the request path or interfering with routing logic.

If you want to see exactly which route is being matched for a given request, you can manually call the matcher’s match method with the problematic path and log the result. This will show you which procedure and path are being selected by the matcher and help you pinpoint where the collision or misrouting is happening.

More details on the matcher and router utilities can be found in the StandardRPCMatcher implementation and router-utils.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[unnoq]

I think by looking at the src you can find a good way to debug: https://github.com/unnoq/orpc/blob/main/packages/server/src/router-client.ts#L27-L71