TypeScript
A strongly typed superset of JavaScript that compiles to plain JavaScript.
Detailed Explanation
TypeScript adds optional static typing to JavaScript, allowing developers to catch errors during development rather than at runtime. It improves developer productivity through better IDE tooling (autocompletion, refactoring) and serves as self-documenting code. It has become the industry standard for large-scale web applications and library development.
Quick Summary
TypeScript is JavaScript with a static type checker bolted on top. The types exist only at build time, the compiler strips them and emits plain JS, but they catch a large class of bugs and unlock first-class editor tooling.
Key Takeaways
- Types are erased at compile time; runtime behavior is identical to the equivalent JavaScript.
- Structural typing: two types are compatible if they have the same shape, not the same name.
- Strict mode (strict: true in tsconfig) is where TypeScript's value lives, anything less and bugs slip through `any`.
- Generics, conditional types, and template literal types make the type system expressive enough to encode many runtime invariants.
- It is the de-facto default for new web projects: Vite, Next.js, Astro, and SvelteKit all assume TS.
When to use it
- Large codebases where refactors must be safe across hundreds of files.
- Library authoring: shipping .d.ts files gives consumers autocomplete and inline docs.
- API clients generated from OpenAPI or GraphQL schemas, end-to-end-typed against the backend.
- Cross-team contracts (shared types in a monorepo) that prevent client/server drift at build time.
Common Mistakes
- Sprinkling `any` to silence the compiler, every `any` is a hole the type system can't help with.
- Treating type assertions (`as Foo`) as casts; they tell the compiler to trust you but do not check anything.
- Modeling runtime data with optimistic types, API responses need parsing/validation (Zod, io-ts) before you can trust the shape.
- Disabling strict and then writing TypeScript that is barely different from JS, you pay the build cost without the benefit.
TypeScript, Frequently Asked
Does TypeScript make my code slower at runtime?
No. The TypeScript compiler outputs plain JavaScript with all type annotations removed. Runtime performance is identical to handwritten JS; the only cost is the build step.
TypeScript vs. JSDoc, which should I use?
TypeScript is better for application code with deep type graphs and tooling needs. JSDoc with `// @ts-check` is enough for small libraries or scripts you don't want to add a build step to. Both run through the same type checker.
Why do TypeScript errors sometimes feel cryptic?
Generic inference produces long, fully-expanded type messages that mention internal helper types. Hovering in the editor and naming intermediate types (`type Foo = ...`) usually makes the error tractable.