Historical Context & Current State

• Node.js released 2009, still doesn't support TypeScript natively
• Alternatives like Deno and Bun got TypeScript support right early
• TypeScript won the ecosystem debate vs Flow
• TypeScript is the standard language for JavaScript tooling ecosystem

TypeScript Support Complexity

• "Supporting TypeScript" means different things:
  • Type checking with error validation
  • Running TypeScript code directly
• TSConfig variations produce different code outputs
• Different interpretations create implementation challenges

TC39 Type Annotations Proposal

• Proposal to add type annotations to vanilla JavaScript spec
• Goal: Copy-paste TypeScript code in browser without transpilation
• Types treated as comments, not enforced/checked
• Current issue: Colon syntax causes "unexpected token" errors in browsers
• Motivation: "Unfork JavaScript" - reduce distance between TypeScript and JS standard
• Address developer friction from custom syntax forks
• Similar to JSDoc comments but integrated into syntax

Historical Type Enforcement Attempts

• 2015: V8 team experimented with "strong mode" (stricter than strict mode)
• Google cancelled experiment due to performance issues
• Type enforcement tends to cause more performance problems than benefits
• Static Hermes project (Facebook/Meta + Amazon) attempting assembly-speed JavaScript
• Current proposal treats TypeScript as comment syntax instead of strict typing

TypeScript Compiler Architecture

• Two separate components:
  • Type checker (validates types, outputs errors)
  • Compiler (generates JavaScript output)
• Type checker can fail while compiler still produces valid JavaScript
• Transpilation (TS→JS) much easier than type checking
• Example: add("Hello", "World") with number types = type error but valid code

Current Development Practices

• Many developers skip type checking during builds
• Separate CI type checking from deployment transpilation
• tsc --noEmit for type checking without output
• Prevents deployment blocking on type errors
• Type checking in CI, transpilation in deployment

Node.js TypeScript Implementation

• New --strip-types flag merged 5 hours ago
• Uses SWC (Rust-based compilation tool) via WebAssembly
• Transpiles TypeScript to JavaScript without type checking
• No external dependencies or loaders needed
• Addresses TS-Node complexity issues

Technical Implementation Details

• Uses @swc/wasm-typescript package (2.5MB vs 115MB native binaries)
• WebAssembly approach avoids multiple platform-specific binaries
• Single WASM file runs on all platforms
• Slightly slower than native but much smaller footprint
• SWC currently used by Next.js and Deno

Limitations & Constraints

• No transformation of TypeScript-specific features
• Enums, namespaces won't work initially
• Only strips types, doesn't convert TS-only syntax
• File extensions mandatory in imports (import file.ts not import file)
• Supports both CommonJS and ES modules
• Module system conversion not performed

Future Implications

• Ecosystem moving toward native TypeScript support
• Reduces need for complex tooling like TS-Node
• Aligns with TypeScript's recommendation for explicit file extensions
• Shows ecosystem maturity and careful implementation approach