Tags
11 articles
Use TypeScript template literal types to encode event names, route patterns, and permission sets directly into your type system — no runtime checks, no string drift.
TypeScript's satisfies operator validates that a value matches a type while preserving literal inference — here's why that distinction matters and where to apply it.
Replace Node's stringly-typed EventEmitter with a generic typed alternative that catches event name typos and payload mismatches at compile time.
Eliminate a whole class of runtime bugs by teaching TypeScript's type system the difference between a UserId and an OrderId — even when both are strings under the hood.
TypeScript's type system stops at compile time — Zod closes the gap by validating data at the runtime boundaries where it actually matters.
Move beyond try-catch soup: discriminated unions, Result types, and error boundaries that make TypeScript codebases more reliable and maintainable.
Advanced TypeScript patterns I rely on daily — discriminated unions, branded types, the builder pattern, and utility types that make large codebases safer and more maintainable.
A practical guide to achieving end-to-end type safety in GraphQL applications using schema-first code generation, covering resolver typing, client-side query types, and eliminating runtime type mismatches between frontend and backend.
A complete tutorial on building end-to-end type-safe APIs using tRPC with Next.js App Router, covering router setup, middleware chains, input validation, and real-time subscriptions.
Walk through building a type-safe form library in TypeScript with runtime validation, field-level error tracking, dirty state management, and a composable API that catches form errors at compile time.
Build a code generator that reads OpenAPI specifications and produces fully typed TypeScript API clients with request validation, error handling, and automatic type inference.