She adds "noErrorTruncation": true because she wants the full horror of a type error when it happens. Let us walk the path of Alessia Exotic through five common architectural near-death experiences. Case 1: The Redux Apocalypse The problem: A large state store with any actions, mutable reducers, and selectors that return unknown . After three months, no one knows what the state actually is.
She is called "Exotic" because her methods seem foreign to the average JavaScript shop. They ask: "Why do we need zod schemas for every API response? The backend is TypeScript too!" Pure-TS - Alessia Exotic - she loves saving the...
"strict": true, "noUncheckedIndexedAccess": true, "exactOptionalPropertyTypes": true, "noImplicitReturns": true, "noFallthroughCasesInSwitch": true, "forceConsistentCasingInFileNames": true, "isolatedModules": true She adds "noErrorTruncation": true because she wants the
She loves saving the architecture.
But ask any CTO who has faced a production meltdown due to a type mismatch. Ask the on-call engineer woken at 3 AM because undefined is not an object . They will tell you: "I wish we had an Alessia. I wish someone had loved the architecture enough to save it from us." Every any is a debt. Every @ts-ignore is a compound interest loan. Alessia pays down that debt early, not because it is glamorous, but because she loves the architecture more than she loves the feature. After three months, no one knows what the state actually is
"rules": "@typescript-eslint/no-explicit-any": "error", "@typescript-eslint/ban-ts-comment": "error"