What are the pros and cons of compiling to JavaScript?

The short answer

Languages like TypeScript, CoffeeScript, and Elm compile (transpile) to JavaScript so they can run in the browser. The main benefit is getting features that JavaScript does not have (like static types). The main cost is a build step, tooling complexity, and the need for source maps to debug.

Why compile to JavaScript

The browser only understands JavaScript (and WebAssembly). If you want to use a different language for web development, it must compile down to JavaScript.

TypeScript — the most popular choice. Adds static types to JavaScript:

Copy
// TypeScript
function add(a: number, b: number): number {
  return a + b;
}
// Compiles to plain JavaScript
function add(a, b) {
  return a + b;
}

Pros

• Type safety (TypeScript) — catches bugs at compile time before they reach production
• Better tooling — autocomplete, refactoring, and error detection in your editor
• Language features — use features that JavaScript does not have yet
• Code quality — types serve as documentation and make code easier to understand

Cons

• Build step — adds compilation time to your workflow
• Debugging complexity — the code in the browser is different from what you wrote. Source maps help but add another layer
• Learning curve — the team needs to learn the language
• Tooling setup — need to configure the compiler, linter, and editor support
• Dependency on the compiler — bugs in the compiler can cause hard-to-debug issues

In practice

TypeScript has become the standard for serious JavaScript projects. The type safety and tooling benefits outweigh the build step cost for most teams. The JavaScript ecosystem has largely embraced it.

Why interviewers ask this

This tests your understanding of the JavaScript ecosystem and build tooling. Interviewers want to see if you understand why languages like TypeScript exist and what the tradeoffs are.