Course contentsShow
← TypeScript
Lesson 1776 of 1,79640. The Future of TypeScriptFree lesson

Timeline and Current Status

Where the proposal stands in the TC39 process and realistic expectations for adoption.

Timeline and Current Status

What you'll learn: Where the JavaScript type annotations proposal stands in TC39's standardization process and what timelines are realistic.

Current Stage in TC39

The Type Annotations Proposal is currently at Stage 1 of TC39's standardization process. This means:

  • The problem is acknowledged as worth solving
  • A champion group is actively developing the proposal
  • The committee has agreed to dedicate time to it

Stage 1 is early. A proposal must progress through Stages 2 (draft specification), 3 (candidate with tests), and 4 (finished) before becoming part of JavaScript.

Realistic Expectations

Years, not months. Major TC39 proposals typically take 3-7 years from Stage 1 to Stage 4. Decorators took nearly a decade. The Type Annotations Proposal involves complex design decisions about what syntax to standardize, how engines should parse it, and which type features remain TypeScript-specific.

The proposal is progressing through iterative design, gathering feedback from TypeScript, Flow, and the broader JavaScript ecosystem. Expect significant evolution in scope and approach.

What This Means for You Today

You don't need to wait. TypeScript works now, and will continue working regardless of standardization. If types become native to JavaScript engines, TypeScript will adapt — but your code won't suddenly break. The transition would be gradual and backward-compatible.

Think of this proposal as a long-term alignment effort, not an imminent revolution.

Key Takeaway: The Type Annotations Proposal is at Stage 1 — early in a multi-year process. TypeScript remains your practical solution today and for years to come.