types not working if input provided

fynn · 2025-07-19T14:11:55.934Z

Hey guys, just getting into tRPC: If i add a input to a query, in the client, the types are not working anymore. thats normal? is there any way around this?

F

fynnOP•7/19/25, 2:13 PM

I am using React Query and the data is just unknown if I add a input to the server query

F

FluX•7/19/25, 2:52 PM

Can you share how you've defined the procedure input and how you are calling the query on the client?

F

fynnOP•7/19/25, 3:49 PM

you mean this?:

export const notificationRouter = router({
    check: publicProcedure
        .input(checkNotificationSchema)
        .query(({ ctx, input }) => {
                  ....
          }),

export const notificationRouter = router({
    check: publicProcedure
        .input(checkNotificationSchema)
        .query(({ ctx, input }) => {
                  ....
          }),

export const notificationRouter = router({
    check: publicProcedure
        .input(checkNotificationSchema)
        .query(({ ctx, input }) => {
                  ....
          }),

export const notificationRouter = router({
    check: publicProcedure
        .input(checkNotificationSchema)
        .query(({ ctx, input }) => {
                  ....
          }),

here's how I call the query:

    const { data } = useQuery(
        trpc.notification.check.queryOptions({ path: pathWithoutLocale, context }),
    );

    const { data } = useQuery(
        trpc.notification.check.queryOptions({ path: pathWithoutLocale, context }),
    );

    const { data } = useQuery(
        trpc.notification.check.queryOptions({ path: pathWithoutLocale, context }),
    );

    const { data } = useQuery(
        trpc.notification.check.queryOptions({ path: pathWithoutLocale, context }),
    );

F

fynnOP•7/19/25, 3:52 PM

just getting into tRPC, so hope thats a good way to do it at all

F

FluX•7/19/25, 4:01 PM

Hm yeah that looks correct. Are your trpc client/server versions mismatched maybe?

F

fynnOP•7/19/25, 4:04 PM

client:

    "@trpc/client": "^11.4.3",
    "@trpc/tanstack-react-query": "^11.4.3",

    "@trpc/client": "^11.4.3",
    "@trpc/tanstack-react-query": "^11.4.3",

    "@trpc/client": "^11.4.3",
    "@trpc/tanstack-react-query": "^11.4.3",

    "@trpc/client": "^11.4.3",
    "@trpc/tanstack-react-query": "^11.4.3",

server:

    "@hono/trpc-server": "^0.4.0",
      "@trpc/server": "^11.4.3",

    "@hono/trpc-server": "^0.4.0",
      "@trpc/server": "^11.4.3",

    "@hono/trpc-server": "^0.4.0",
      "@trpc/server": "^11.4.3",

    "@hono/trpc-server": "^0.4.0",
      "@trpc/server": "^11.4.3",

so yeah, everythings matching. whats weird is that it only cant infer types if I add the .input on the query - without, it works. also on mutations the input is just working fine

F

FluX•7/19/25, 4:07 PM

That's weird. In my project I have the exact same setup: Hono, trpc, etc and I don't have this issue.
Could it be that the keys

path

path

and/or

context

context

of your input object cause problems? Or anything else in the input object? That's my only guess

F

FluX•7/19/25, 4:09 PM

... that is, if only that particular query is affected and other queries work

FFluX That's weird. In my project I have the exact same setup: Hono, trpc, etc and I d...

F

fynnOP•7/19/25, 4:13 PM

don't think so, I mean its the same with just a simple zod string.

its not particular only this one, every query where I try to use a input has the problem. mutations are working, and queries without an input aswell

F

FluX•7/19/25, 4:17 PM

What's your Typescript and tanstack/react-query versions?

F

fynnOP•7/19/25, 4:36 PM

typescript 5.8.3, react query 5.83.0 atm