Add approved trace files for payload, @trpc/server, @trpc/client, zod, superjson, @payloadcms/db-postgres, @payloadcms/richtext-lexical, globals, react, react-dom, vitest, @tanstack/react-query, and all @testing-library/* packages. All traces dated 2026-05-14, decision: approved, adr: null. Establishes the baseline so the pre-commit library-decisions gate is additive (new deps require traces) rather than disruptive (old deps fail immediately). All 34 trace files pass validateTrace() from schema.mjs. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
3.0 KiB
package, version, tier, decision, date, deciders, adr, filter-results, verification-commands, accepted-cves
| package | version | tier | decision | date | deciders | adr | filter-results | verification-commands | accepted-cves | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| @tanstack/react-query | ^5.59.0 | core | approved | 2026-05-14 |
|
null |
|
|
Filter: license
npm view @tanstack/react-query license returns MIT. MIT is on the allowlist.
Filter: types
@tanstack/react-query is authored in TypeScript and ships its own .d.ts declaration files. No separate @types/ package is needed.
Filter: maintenance
Actively maintained by the TanStack team. The 5.x line is the current stable major. Regular releases; strong community adoption alongside tRPC.
Filter: boundary-fit
@tanstack/react-query is listed as a runtime dependency of @repo/core-testing to provide the QueryClient and QueryClientProvider needed when rendering components that use TanStack Query hooks in tests. The production apps consume it through their framework layer. No boundary rule restricts React Query to a specific tier.
Filter: shadow-check
@tanstack/react-query is the sole server-state management library in the workspace. No competing library (SWR, Apollo Client, RTK Query, etc.) is present for the same purpose.
Filter: eu-residency
@tanstack/react-query is a pure client-side state management library with no network communication to vendor-controlled endpoints. EU residency does not apply.
Filter: cve-scan
pnpm audit --audit-level=moderate reports no advisories against @tanstack/react-query at the time of this trace.
Filter: named-consumer
@repo/core-testing uses @tanstack/react-query to set up QueryClient wrappers for component tests. The Next.js app uses TanStack Query for client-side data fetching with tRPC. Named, non-hypothetical consumers exist today.
Prompt: replaces
@tanstack/react-query replaces manual useEffect + useState patterns for server-state caching, deduplication, and background refetching. It is the standard companion to tRPC's React adapter.
Prompt: migration-cost-out
Hard. TanStack Query's useQuery / useMutation hooks are used in feature UI components across the Next.js app. The cache key structure (trpc.* query keys) is tightly coupled to tRPC's query key format. Migrating out requires replacing all data-fetching hooks and the cache invalidation strategy.
Prompt: alternatives-considered
- SWR — Similar feature set but less integration with tRPC's query key format; TanStack Query's devtools and cache invalidation API are more expressive.
- Apollo Client — GraphQL-centric; incompatible with tRPC's RPC model.