omk-typescript-strict

Enforce strict TypeScript mode by setting strict: true, avoiding any and unsafe casts, mandating explicit return types, and using discriminated unions for state machines. This prevents weak typing and boundary violations across Next.js and NestJS codebases.

Validate DTOs and prevent ORM entity leakage by keeping NestJS controllers thin, placing business logic in services, and validating route and search params. This ensures boundary-safe API responses without exposing unchecked data.

Maintain Next.js server and client boundaries by making separation explicit and validating route and search params instead of relying on unchecked values. This prevents runtime bugs caused by weak typing and unclear boundaries.

Yes, this strict TypeScript review approach applies to Node.js and React workflows. It covers DTO validation, API response design, and state-machine modeling, requiring strict: true assumptions and evidence of boundary-safe code.

Inconsistent TypeScript configuration causes hidden runtime bugs because weak typing and unclear boundaries across full-stack frameworks go unchecked. Avoiding any and unsafe assertions while enforcing strict mode prevents fragile code and slow reviews.

Standardize TypeScript code review output by producing a report covering type issues, boundary issues, unsafe casts, and suggested fixes. This provides a consistent review format for full-stack projects.