feat: Passing createCaller return value to trpc.Provider about trpc HOT 4 CLOSED

useQuery calls client.query by default:

But it's not using proxy so maybe that's why it works then 😅

from trpc.

I think you should be able to do this with a custom link, that way you wont make http requests during SSR:

const context = createContext(req);

const trpcClient = trpc.createClient({
  links: [
    () =>
      ({ op }) =>
        observable((observer) => {
          callProcedure({
            procedures: appRouter._def.procedures,
            path: op.path,
            input: op.input,
            ctx: context,
            type: op.type,
          })
          .then((data) => {
            observer.next({ result: { data } });
            observer.complete();
          })
          .catch((cause: TRPCErrorResponse) => {
            observer.error(TRPCClientError.from(cause));
          });
        }),
  ],
});

(despite the types not matching, passing the createCaller does work for me)

This seems weird as createCaller and a client doesn't have the same call signatures (no .query() in createCaller).

from trpc.

Perfect, that works, thanks! I think client.query is just never called in my case. I am using useSuspenseQuery so it seems like it is calling useQuery on the recursive proxy. I guess client.query is only called when not using react-query

Feel free to close this issue if its not something that fits

from trpc.

This issue has been locked because we are very unlikely to see comments on closed issues. If you are running into a similar issue, please create a new issue. Thank you.

from trpc.