Use satisfies before you reach for as in TypeScript

The TypeScript keyword I see misused most is as. Most of the time you wanted satisfies, which checks the shape and keeps the narrow type.

What as actually does

Every as SomeType is you telling the compiler to stop checking. Sometimes you need that. Usually you do not.

type Config = { port: number; host: string };
 
// Compiles fine, even though host is missing
const a = { port: 3000 } as Config;
 
// Error: property 'host' is missing
const b = { port: 3000 } satisfies Config;

What satisfies gives you

satisfies validates the value against the type and leaves the inferred type alone. You get the check and you keep the precise literal types, instead of widening everything to the annotation.

const routes = {
  home: "/",
  blog: "/blog",
} satisfies Record<string, string>;
 
routes.home; // still known to exist, typed as string

The rule I give my team

If you write as, write a comment explaining why the compiler is wrong. If you cannot write that comment, the compiler is not wrong.

The codebase got noticeably safer after we started enforcing that one habit in review.

Takeaways

• as turns off type checking for that expression.
• satisfies checks the shape and keeps the narrow inferred type.
• Every as should come with a comment explaining why the compiler is wrong.
• Enforcing this in review is a cheap, effective safety habit.