anti-patterns

Avoid pnpm.overrides, yarn resolutions, and npm overrides as first solutions since they create version conflicts and technical debt. Instead, update dependencies through proper package manager commands and use semantic version ranges to resolve transitive dependency issues.

Use inline suppression only as a last resort after trying three alternatives: change the code so the rule no longer triggers, reconfigure the rule if its default is wrong, or define a scoped exception for a legitimately exempt category. Always write a rationale naming the rule and rejected alternatives.

Yes, an any type or type assertion silences the type checker the same way a comment directive silences a linter, without changing runtime behavior. The same ladder applies: model the actual type, or return unknown and let the caller narrow it.

Placing safe operations like string concatenation or variable assignment inside try/catch obscures which operation can actually fail. Only wrap operations that can throw so error handling intent remains clear to readers and maintainers.

Quick fixes and band-aid patches address symptoms rather than root causes, accumulating maintenance burden over time. Configuration shortcuts that bypass intended workflows also break when the underlying tooling changes, making them unreliable long-term.