The Iteration Plan and GitHub Projects
You'll learn: Where TypeScript's official development roadmap lives and how to follow what's coming next.
What You'll Discover
TypeScript's development is remarkably transparent. Unlike some open-source projects where future plans remain opaque until release, TypeScript publishes detailed iteration plans that outline what the team is working on for each upcoming version.
These plans live in the official TypeScript GitHub repository as markdown documents and GitHub Project boards, giving you a window into priorities, timelines, and design discussions.
Where to Find the Roadmap
The primary sources are:
1. Iteration Plan Issues: The TypeScript team creates GitHub issues labeled "Planning" for each release cycle. Search for "Iteration Plan" in the microsoft/TypeScript repository issues. For example, you might find "TypeScript 5.4 Iteration Plan" as a detailed breakdown.
2. GitHub Projects Board: Navigate to the "Projects" tab in the TypeScript repository. You'll see boards organizing work items by milestone, priority, and status (e.g., "To Do," "In Progress," "Done").
3. The Official Blog: Major features and release themes are announced on devblogs.microsoft.com/typescript, often referencing iteration plans for details.
Reading the Iteration Plan
Each iteration plan typically includes:
- High-priority features the team commits to investigating or shipping
- Investigations for experimental features (like those TC39 proposals you learned about)
- Bug fixes and polish scheduled for that version
- Community requests being considered
- Links to related design discussions
The plans are living documents—they evolve as priorities shift based on community feedback, technical challenges, or ECMAScript developments.
Why This Matters
Following the iteration plan helps you anticipate breaking changes, understand why certain features are prioritized, and even participate in early design feedback through linked GitHub discussions.
Key Takeaway: TypeScript's iteration plans and GitHub Projects provide a transparent, constantly updated view of what's being built, investigated, and prioritized—making it easy to stay ahead of language evolution.