Skip to main content

Why Use TypeScript

The short answer: type safety​

TypeScript keeps your application free from a whole class of bugs — the ones where a value turns out to be the wrong shape at runtime. Languages like C#, Java, C, C++ are type-safe in the same spirit; TypeScript brings that safety to JavaScript.

Concretely, it protects you from:

  • Type errors — passing a string where a number was expected, calling a method that doesn't exist.
  • null / undefined surprises — the "cannot read property of undefined" family of crashes.

Why it fits JavaScript so well​

  • Compiles to plain JavaScript. The output is normal JS that runs anywhere JS runs.
  • Keeps your code evergreen. You write modern syntax; the compiler targets whatever JS version you need.
  • Supported by every major library and framework. React, Angular, Vue, Node — all ship first-class types.

Key insight — types are erased at compile time

TypeScript's types exist only while checking. When your code is converted to JavaScript, every type is stripped out. Nothing about types survives to runtime.

function greet(name: string): string {
  return `hi ${name}`;
}
// emitted JS — types gone:
// function greet(name) { return `hi ${name}`; }

This is why you can't check a TypeScript type at runtime (if (x is User) doesn't exist). Types guide the compiler, then vanish.

TypeScript's value is a stricter editor and build step, not a heavier runtime. You pay at compile time and ship the same lightweight JavaScript.