Features Explicitly Out of Scope
What you'll learn: Which TypeScript-specific features will never become part of the JavaScript standard, even if type annotations do.
The Core Idea
While the Type Annotations Proposal aims to let browsers parse and ignore types without transpilation, not all TypeScript features are candidates for standardization. Some features don't just annotate types—they change JavaScript's runtime behavior or add entirely new constructs. These features are explicitly out of scope for the proposal and will always require transpilation.
Why Some Features Are Excluded
The Type Annotations Proposal has a strict rule: types should be ignored, not executed. Any TypeScript feature that introduces new runtime behavior, syntax that does more than annotate, or constructs that don't exist in JavaScript fundamentally conflicts with this goal.
Key Features That Won't Become JavaScript
Enums
Enums generate actual runtime objects with reverse mappings (for numeric enums). They're not just type annotations—they're data structures:
// TypeScript enum (out of scope)
enum Status {
Active,
Inactive
}
// Compiles to runtime code
// JavaScript would have no idea what to "ignore" here
Alternative: Use string literal unions or plain objects with as const, which are already valid JavaScript patterns.
Namespaces
Namespaces are an organizational construct from TypeScript's early days that emit actual JavaScript objects and nested structures. They modify the runtime environment.
Alternative: Use ES modules (import/export), which are standardized JavaScript.
Parameter Properties
Shorthand syntax like constructor(public name: string) that automatically creates and assigns class properties doesn't exist in JavaScript and requires code transformation.
Alternative: Write the properties and assignments explicitly.
Legacy Features
Several older TypeScript features like module keyword syntax and triple-slash directives for dependencies are also out of scope—they're specific to TypeScript's historical module system.
The Dividing Line
Think of it this way: if removing the feature would change what your code does at runtime, it's out of scope. Type annotations, interfaces, and type aliases just describe—enums and namespaces create.
Key Takeaway: Enums, namespaces, parameter properties, and other runtime-affecting TypeScript features will never be part of JavaScript's standard and will always require transpilation, even if basic type annotations become ignorable syntax.