What are best practices for strict type safety and avoiding 'any' in TypeScript?

Explanation & Concept

1. Replace `any` with `unknown` for values of unknown origin, forcing type validation before use. 2. Enable `strict: true` in tsconfig. 3. Use `as const` for immutable lookup arrays. 4. Avoid type assertions (`as Type`) unless interfacing with dynamic DOM APIs or legacy code. 5. Leverage Discriminated Unions for state management.

Code Example

typescript

// UNHEALTHY: Bypasses compiler
function parseBad(raw: any) {
  return raw.toUpperCase(); // Runtime crash if raw is not string!
}

// HEALTHY: Forces type guard check
function parseSafe(raw: unknown): string {
  if (typeof raw === "string") {
    return raw.toUpperCase(); // Safe!
  }
  throw new Error("Expected string input");
}

How It Works & Key Takeaways

Using `unknown` instead of `any` ensures that all dynamic runtime inputs are safely validated before operations are performed.