typescript-patterns

name	typescript-patterns
description	TypeScript patterns — type system best practices, strict mode, utility types, generics, discriminated unions, error handling with Result types, and module organization. Core patterns for production TypeScript.

TypeScript Patterns

Production-grade TypeScript patterns for type-safe, maintainable applications.

When to Activate

• Writing TypeScript code in any framework (Node.js, React, Next.js)
• Designing type-safe APIs and domain models
• Handling errors without exceptions
• Structuring TypeScript modules and configurations
• Replacing runtime any types or unsafe as casts with properly narrowed types
• Modeling complex state machines or API response shapes using discriminated unions
• Setting up a strict tsconfig.json for a new project to prevent common runtime errors

TypeScript Configuration

Strict tsconfig.json

Enable strict plus these additional checks:

{
  "compilerOptions": {
    "target": "ES2022", "module": "NodeNext", "moduleResolution": "NodeNext",
    "strict": true,
    "noUncheckedIndexedAccess": true,
    "exactOptionalPropertyTypes": true,
    "noImplicitReturns": true,
    "noFallthroughCasesInSwitch": true,
    "noUnusedLocals": true,
    "noUnusedParameters": true,
    "esModuleInterop": true,
    "declaration": true, "declarationMap": true, "sourceMap": true
  },
  "include": ["src/**/*"],
  "exclude": ["node_modules", "dist", "**/*.test.ts"]
}

Core Type System Patterns

Prefer interface for Object Shapes

// Good: interface for objects (extensible, better error messages)
interface User {
  id: string;
  name: string;
  email: string;
  createdAt: Date;
}

// Good: type alias for unions, intersections, computed types
type UserId = string;
type AdminUser = User & { role: 'admin'; permissions: string[] };
type UserOrAdmin = User | AdminUser;

Discriminated Unions

The most powerful TypeScript pattern for modeling state machines and API responses:

// Model all states explicitly
type LoadingState =
  | { status: 'idle' }
  | { status: 'loading' }
  | { status: 'success'; data: User[] }
  | { status: 'error'; error: Error; message: string };

// Exhaustive switch with never check
function renderState(state: LoadingState): string {
  switch (state.status) {
    case 'idle':    return 'Ready';
    case 'loading': return 'Loading...';
    case 'success': return `Loaded ${state.data.length} users`;
    case 'error':   return `Error: ${state.message}`;
    default: {
      const _exhaustive: never = state;  // Compile error if case missing
      return _exhaustive;
    }
  }
}

// Domain events with discriminated unions
type  =
  | { : ;    : ; : [] }
  | { : ;      : ; :  }
  | { : ;   : ; :  }
  | { : ; : ; :  };

Literal Types and Const Assertion

// Literal types for enumerating values
type Direction = 'north' | 'south' | 'east' | 'west';
type HttpMethod = 'GET' | 'POST' | 'PUT' | 'PATCH' | 'DELETE';

// const assertion — preserves literal types
const ROUTES = { home: '/', users: '/users', products: '/products' } as const;
type Route = typeof ROUTES[keyof typeof ROUTES];  // '/' | '/users' | '/products'

// Prefer const objects over enum — see Anti-Pattern below

Generics

// Generic with constraint
function getProperty<T, K extends keyof T>(obj: T, key: K): T[K] {
  return obj[key];
}

// Generic container
interface Repository<T, Id = string> {
  findById(id: Id): Promise<T | null>;
  findAll(): Promise<T[]>;
  save(entity: T): Promise<T>;
  delete(id: Id): Promise<void>;
}

// Generic with default
interface PaginatedResult<T> {
  data: T[];
  meta: { total: number; page: number; limit: number; hasNext: boolean };
}

function paginate<T>(items: T[], page: number, limit: number): PaginatedResult<T> {
  const start = (page - 1) * limit;
  return { data: items.slice(start, start + limit), meta: { : items., page, limit, : start + limit < items. } };
}

Utility Types

interface User {
  id: string;
  name: string;
  email: string;
  password: string;
  createdAt: Date;
}

// Partial — all fields optional (e.g., update DTOs)
type UpdateUserDto = Partial<Omit<User, 'id' | 'createdAt'>>;

// Required — all fields required
type CompleteUser = Required<User>;

// Pick — select subset of fields
type PublicUser = Pick<User, 'id' | 'name' | 'email'>;

// Omit — exclude fields
type UserWithoutPassword = Omit<User, 'password'>;

// Record — typed object map
type UsersByEmail = Record<string, User>;
const cache: UsersByEmail = {};

// Readonly — immutable object
type ImmutableUser = <>;


  (): <> { ... }
  = << fetchUser>>;  
  = < fetchUser>;           


  = <, { :  |  }>;
  = <, { :  |  }>;


  = < |  | >;  

Error Handling with Result Types

Avoid throwing exceptions for expected errors. Use Result/Either types instead:

// Simple Result type
type Result<T, E = Error> =
  | { ok: true;  value: T }
  | { ok: false; error: E };

// Constructors
const Ok  = <T>(value: T): Result<T, never>  => ({ ok: true,  value });
const Err = <E>(error: E): Result<never, E>  => ({ ok: false, error });

// Usage — narrowed by discriminant
const result = parseUserInput(body);  // Result<User, ParseError>
if (!result.ok) {
  return res.status(400).json({ error: result.error.message });
}
const user = result.value;  // TypeScript knows this is User here

Async Result

type AsyncResult<T, E = Error> = Promise<Result<T, E>>;

// Wrap async calls: catch all exceptions → Err, return Ok on success
async function fetchUser(id: string): AsyncResult<User, ApiError> {
  try {
    const response = await fetch(`/api/users/${id}`);
    if (!response.ok) return Err({ code: response.status, message: response.statusText });
    return Ok(await response.json() as User);
  } catch (err) {
    return Err({ code: 0, message: 'Network error' });
  }
}

Branded Types (Nominal Typing)

Prevent mixing up values of the same underlying type:

// Brand: make string subtypes incompatible
type Brand<T, B extends string> = T & { readonly _brand: B };

type UserId    = Brand<string, 'UserId'>;
type ProductId = Brand<string, 'ProductId'>;
type Email     = Brand<string, 'Email'>;

// Constructors with validation
function UserId(id: string): UserId {
  if (!id.trim()) throw new Error('UserId cannot be empty');
  return id as UserId;
}

function Email(email: string): Email {
  if (!email.includes('@')) throw new Error('Invalid email');
  return email as Email;
}


 (): <> { ... }

 uid = ();
 pid = ();

(uid);  
(pid);  

Module Organization

src/
├── domain/           # Pure domain types and logic (User, Order, value objects)
├── application/      # Use cases / service layer
├── infrastructure/   # External adapters (DB, HTTP, email)
├── api/              # HTTP controllers/routes
└── shared/           # Shared utilities (Result, pagination)

Each layer has an index.ts with explicit named exports — never export * from './internal'. See Anti-Pattern: "Exporting Bare Types Without a Public API Surface" below.

Quick Reference

Pattern	When to Use
interface	Object shapes, classes, extensible APIs
type	Unions, intersections, computed types, aliases
Discriminated union	State machines, response types, events
as const	Constant object/array with literal types
Result type	Expected errors (validation, not-found, network)
Branded types	IDs, emails — prevent passing wrong string type
noUncheckedIndexedAccess	Force null-check on array/object access
Readonly<T>	Immutable domain objects
Partial<T>	Update/patch DTOs
Omit<T, K>	Strip sensitive fields from output types

Anti-Patterns

Using any to Silence Type Errors

Wrong:

function processResponse(data: any) {
  return data.user.name.toUpperCase() // no safety — crashes at runtime
}

Correct:

interface ApiResponse {
  user: { name: string }
}

function processResponse(data: unknown): string {
  if (typeof data !== 'object' || data === null || !('user' in data)) {
    throw new Error('Invalid response shape')
  }
  return (data as ApiResponse).user.name.toUpperCase()
}

Why: any disables the type checker entirely; unknown forces explicit narrowing and keeps runtime safety intact.

Using TypeScript enum Instead of Const Objects

Wrong:

enum OrderStatus {
  Draft = 'DRAFT',
  Pending = 'PENDING',
  Shipped = 'SHIPPED',
}
// Generates runtime JS, numeric members are unsafe, not iterable easily

Correct:

const OrderStatus = {
  Draft:   'DRAFT',
  Pending: 'PENDING',
  Shipped: 'SHIPPED',
} as const

type OrderStatus = typeof OrderStatus[keyof typeof OrderStatus]

Why: Const objects are plain JS values (zero runtime overhead), tree-shakeable, and produce better discriminated union types than enums.

Throwing Exceptions for Expected Error Cases

Wrong:

async function getUser(id: string): Promise<User> {
  const user = await db.findById(id)
  if (!user) throw new Error('User not found') // caller must know to catch
  return user
}

Correct:

async function getUser(id: string): AsyncResult<User, NotFoundError> {
  const user = await db.findById(id)
  if (!user) return Err({ code: 'NOT_FOUND', message: `User ${id} not found` })
  return Ok(user)
}

Why: Exceptions for predictable cases (not-found, validation) make error handling invisible to callers; Result types make it explicit and type-checked.

Widening Types With Type Assertions (as) Instead of Narrowing

Wrong:

const config = JSON.parse(raw) as AppConfig // no validation — runtime bomb
const userId = req.params.id as UserId       // bypasses brand check

Correct:

const parsed = AppConfigSchema.parse(JSON.parse(raw)) // zod/valibot validate
const userId = UserId(req.params.id)                  // branded constructor validates

Why: as casts are lies to the compiler — they shift type errors from compile-time to runtime; always validate at system boundaries instead.

Exporting Bare Types Without a Public API Surface

Wrong:

// Re-export everything — callers couple to internals
export * from './user'
export * from './order'
export * from './internal-helpers' // leaks implementation details

Correct:

// domain/index.ts — explicit, intentional public API
export type { User, UserId } from './user'
export type { Order, OrderStatus } from './order'
export { createUser, validateEmail } from './user'
// internal-helpers NOT exported

Why: Star re-exports make every internal symbol part of the public API, increasing coupling and preventing safe refactoring.

For advanced patterns — mapped types, template literal types, conditional types, infer, type guards & narrowing, decorator patterns, async patterns, testing with vitest/jest, and performance optimization — see skill: typescript-patterns-advanced. For testing patterns — unit tests with vitest, mocking with vi.mock, integration tests, and coverage setup — see skill: typescript-testing.