trpc react-query hooks api-clients migration

tRPC drops abstraction layer for React Query

New tRPC client uses native TanStack Query interfaces (QueryOptions, MutationOptions) instead of wrapper hooks, eliminating a confusing abstraction layer.

Summary

Removes cognitive friction for developers already using TanStack Query elsewhere in their app—you follow the same patterns instead of learning tRPC-specific syntax. Also fixes a hooks-linting issue in the classic client that breaks under React Compiler.

Why it matters

Implementation verdict

Replaces the classic tRPC React Query integration (still maintained but no new features). Requires: tRPC next-release, refactoring useQuery/useMutation calls to use .queryOptions()/.mutationOptions() factories. Both clients coexist, so gradual migration is viable. Ready now for new projects; existing projects should migrate incrementally.

Sources

1.new TanStack React Query integration for tRPC is now available on tRPC's next-release
2.choosing to utilize the QueryOptions and MutationOptions interfaces native to TanStack React Query
3.removing a layer of abstraction which is a common source of confusion for new users
4.Our classic React Query integration actually breaks the rules of hooks; it cannot be correctly linted
5.Both clients are compatible with each other and can exist in the same application

Dev Signal

Get briefs like this in your inbox — free, 3x a week.

100+ sources compressed into one 4-minute read. Ranked, cited, implementation-ready.

Read the full issue →All briefs