ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #trpc
Learn how to enforce JWT‑based authentication in tRPC using middleware. This guide walks through a concrete example, shows how context is injected, and discusses trade‑offs and best practices.
Build a minimal, type‑safe tRPC layer with Zod validation and middleware‑based auth for same‑origin apps. This guide covers requirements, design, trust boundaries, ops checks, failure modes, and when to pivot to a different API stack.
tRPC uses TypeScript's infer keyword to derive client types directly from the server router—no code generation, no OpenAPI sync, just shared types that catch contract drift at compile time.
When tRPC’s type inference breaks, your router may compile but callers receive wrong or missing types. This guide walks through the symptoms, root causes, step‑by‑step checks, and fixes—plus a concrete example of a nested router that preserves full type safety.
tRPC replaces generated SDKs and OpenAPI specs with a single exported type. Here's how the inference works, a minimal working example, and the monorepo coupling trade-off you need to price in.
Use tRPC middleware to centralize authentication, enrich context with a typed user object, and keep resolvers clean—without losing type inference or adding measurable latency.
A decision guide to tRPC client transports: when httpBatchLink is enough, when streaming or SSE subscriptions earn their place, and how to route both through one splitLink client.
Need real‑time data without duplicating logic? tRPC’s experimental WebSocket support lets you share a single router for REST and real‑time APIs. Follow a concrete example, see the trade‑offs, and learn how to deploy it safely.
Stop fighting API drift. Learn how tRPC uses TypeScript inference and Zod to synchronize server and client types without manual code generation.
typescript