Has anyone got the react query go to definition working?

[ElasticBottle]

Is it possible to have go to definition enabled?

I have a react query orpc client set up, but clicking on todos or create in the rqApiClient brings me to the rqApiClient itself instead of the place where the create function was created.

has anyone been able to work around this?

// using the react query plugin
const { mutate: addTodo } = useMutation(
    rqApiClient.todos.create.mutationOptions({
      onSuccess: () => {
        refetch();
        setTodo("");
      },
    }),
  );

// in another file
export const rpcClient: Router = createORPCClient(
  new RPCLink({ url: "/api/rpc" }),
);
export const rqApiClient = createORPCReactQueryUtils(rpcClient);

using the rpcClient directly works fine, but using the rqApiClient doesn't

[dosubot[bot]]

This is a known limitation: 'go to definition' doesn't work with rqApiClient because createORPCReactQueryUtils builds the client using JavaScript's Proxy and dynamic property access, which TypeScript and most IDEs can't statically analyze for navigation features like 'go to definition'—property resolution happens at runtime, not compile time. This trade-off enables deep type inference and flexible APIs, but breaks static navigation. There aren't any documented workarounds or plugins to restore this; if 'go to definition' is critical, using the base rpcClient directly is the only reliable way to get that feature back. More details on the design and its trade-offs are discussed here and the implementation can be seen here. If you have a specific workflow in mind, I can help brainstorm alternatives!

To reply, just mention @dosu.

---

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

[unnoq]

It should work, can you help me create a minimal repro?

[ElasticBottle]

yeap, I'll try to create one within the week and share it here

[ElasticBottle]

@unnoq dug a little deeper and figured out the issue

I have a monorepo that was emitting types to help the TS LSP. removing the type emission sovled the issue.

Do wonder if we can support type mapping from the emitted types though.

Side notes, Notice a tanstack-query and a react-query package. Worth adding some docs to let folks know that react-query is outdated and that they should use tanstack-query package instead.

[unnoq]

@ElasticBottle You should config emit declaration map file something like .d.ts.map can solve this problem

[ElasticBottle]

Interesting, I thought I had that configured, will double check