typescript-debugger

Type errors without `any` or `as` require identifying the root cause: check if the value needs narrowing, use discriminated unions, apply `as const` for literals, or validate with tools like valibot. Work through documentation and existing issues first; `any` masks the real problem and breaks type safety.

Refactor systematically by addressing type errors one at a time, replacing unsafe patterns (`any`, `as`, `!`) with safe alternatives like `satisfies`, built-in narrowing, and const assertions. This ensures each fix improves safety without introducing new issues or compromising code quality.

Use discriminated unions to create type-safe exhaustive patterns with literal types; use `as const` to narrow object or array types to their exact literal values. Both enable robust type inference and eliminate the need for unsafe assertions like `as` or non-null `!`.

Yes, valibot validates runtime data against TypeScript types without overhead. Use it during library and API development to enforce type contracts, catch mismatches early, and guide users toward safe type narrowing instead of bypassing checks with `any`.

These constructs bypass type safety and hide errors, causing unpredictable runtime failures. They prevent the type system from catching bugs early and make refactoring risky. Type-safe alternatives like narrowing, `satisfies`, and validators provide better protection without performance overhead.

Apply a checklist approach: avoid `any`, `as`, `!`, and unsafe patterns; promote `as const`, discriminated unions, and built-in narrowing; persist through documentation and issue searches before escalating. This ensures reviewers catch anti-patterns early and enforce consistent type-safety practices across the codebase.