Alessia loves effect-ts , zod , typia , and ts-pattern . She avoids lodash (inferior typing) and treats mongoose schemas with suspicion. Her tsconfig is not the default "strict": true . It is:
She saves the architecture by making it : a codebase where the TypeScript compiler is not a suggestion but a law. Part 2: What Is "Pure-TS"? Beyond the Buzzword "Pure-TS" is often misunderstood as simply "writing TypeScript without JavaScript." That is trivial—just ban .js imports. Pure-TS - Alessia Exotic - she loves saving the...
const getUser = (input: unknown): User => UserSchema.parse(input); Alessia loves effect-ts , zod , typia , and ts-pattern
| Category | Library | Why Alessia Loves It | | :--- | :--- | :--- | | | zod or typia (compile-time) | Runtime enforcement with compile-time inference | | Error handling | neverthrow or effect | No implicit exceptions; Result types everywhere | | Pattern matching | ts-pattern | Exhaustiveness checking: the compiler ensures all cases handled | | FP utilities | fp-ts (with strict linting) | Pure functions, no side effects | | HTTP client | fetch + zod (no abstractions) | She controls the parsing layer completely | | State management | xstate (v5 with typegen) | State machines that cannot reach invalid states | | Database | drizzle-orm or prisma | Typed queries, sql tagged templates with type safety | It is: She saves the architecture by making
Alessia insists: "If you cannot parse it, you cannot trust it." Pure-TS codebases prefer libraries that ship first-party TypeScript types (not @types/ ). Even better: libraries written entirely in TypeScript with isolatedModules compatibility.
Alessia smiles. She knows the backend can change. She knows the network lies. She knows that trust is not a type. Architecture rots from the top down but fails from the bottom up. A missing readonly here, a mutable export there—these are the cracks through which runtime exceptions flood. Alessia loves not the glory of new features but the invisible labor of structural integrity .