Common TypeScript Anti-Patterns Identified

- A primary anti-pattern is the overuse of the `any` type, which effectively disables TypeScript's static type checking for a variable, increasing the risk of runtime errors that the language is designed to prevent. - Many developers incorrectly assume TypeScript's compile-time checks provide runtime data validation, a misunderstanding that can lead to significant security vulnerabilities if server responses or user inputs are not explicitly validated at runtime. - Excessive use of type assertions, using the `as` keyword, is a common smell that indicates a developer is overriding the type system's inferences, potentially masking type mismatch bugs that would otherwise be caught by the compiler. - While TypeScript itself doesn't add a performance burden as it compiles to JavaScript, anti-patterns can impact performance; for example, unused variables and functions can bloat bundle sizes, increasing load times for end-users. - The official TypeScript documentation explicitly warns against using primitive wrapper types like `String` or `Number` (with a capital letter), as these refer to object wrappers with surprising behavior, such as `new Boolean(false)` evaluating to `true`. - TypeScript 5.6 introduced stricter checks that flag conditional expressions that are always truthy or nullish, helping to identify dead code or logical errors from syntactical mistakes. - Developers transitioning from class-based languages like Java or C# often introduce an anti-pattern by overusing classes for scenarios where interfaces and object literals would be simpler and more idiomatic in JavaScript. - To combat unused variables, TypeScript provides compiler options like `--noUnusedLocals` and `--noUnusedParameters`, though ESLint rules like `@typescript-eslint/no-unused-vars` are often preferred for their higher configurability.