TypeScriptTips

Make bugs impossible.
One TypeScript tip at a time.

I like the tricks :) – Kasia

Do not throw

@RiccardoOdone•Suggest a tip•

Model operations that could fail with a type, so that you can't forget to catch.

const couldFail = () => {
  throw new Error("Boom") // ⛔️ Oops, forgot to catch
}

type Result<Error, Value> =
  { _kind: "ok", value: Value } |
  { _kind: "error", value: Error }

  const couldFail = (): Result<string, number> => {
    return { _kind: "ok", value: 1 } // or
    return { _kind: "error", value: "no worries!" }
  } // ✅ You cannot forget to handle the error
Type-safe carouselDo not throwFilter using a type assertionUse precise typesType-safe string templatingEnumerating a union typeNumbers with unitsZero nullEnumerating statusesAnd typesAvoiding window as anyUse descriptive valuesCheck authorization with typesExtract union types from record typesKeep in sync with conditional typesType-safe pickPass arguments by namePick instead of duplicatingPrevent mutationsType aliasesModel with different typesPrefer static types over testsPush conditionals downType-level functionsCheck Authorization With Types (again)From Union to TupleLimit typesLaser-focused typesCallable typesPartial considered harmfulSatisfy typesWTH?!Parse, don't castNarrow typesFetch footgunModel with different types (2)Polymorphic typesParse, don't cast (again)Type-safe envObject vs Recordconst Type ParametersDigType checksExpand intellisenseNumbers with units (2)Unchecked indexed accessExtract instead of duplicating

TypeScriptTips

Crafted with 💛 by Riccardo