microsoft / microsoft/TypeScript
TypeScript 7.1 Iteration Plan
Open
Nobody has claimed this yet.
Planning
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
| Date | Milestone |
|---|---|
| 2026-10-02 | Beta Prep |
| 2026-10-06 | 7.1 Beta Release |
| 2026-11-06 | RC Prep |
| 2026-11-10 | 7.1 RC Release |
| 2026-11-20 | Stable Prep |
| 2026-11-24 | 7.1 Stable Release |
Language and Compiler
- Stabilize API
- Content Mapper API
- Emit API
- Language Service API
- Support
typeOn Import Attributes - Investigate Node 26 Package Maps
- Add
es2026option forlibandtarget - Support Source Phase Imports
lib.d.tsUpdates for New Iterator MethodsPromise.allKeyedandPromise.allSettledKeyedlib.d.tsUpdates for DOM
Editor Productivity
- Replace Existing API Integrations in VS Code
- Investigate New Expandable Hover API in LSP
- Investigate Multi-document Highlighting API in LSP
- Investigate Region Diagnostics in LSP
Performance
- Faster Union Type Construction
- Lazily Collect Source File Identifiers
- Fast Path for Assignment Narrowing on Unions
- Fast Path for Equality &
switch/caseNarrowing on Unions - Optimize Representations of Checker-Specific Side-Tables
- Experiment with Algorithms for Distributing Files Across Type-Checkers
- Probably more!
Infrastructure
- Static Analysis for Nil Checking and Casts
- Migrate repository to microsoft/TypeScript
- Overhaul of Publishing Pipeline
- Publish wasm (wasip1?) Build
- Publish Android ARM64 Build
- Flaky Diagnostics Detection
Website
- Monaco LSP Feedback
- Getting Playground Running with wasm
- Speed up website builds
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the milestone table and review the linked TypeScript issues and typescript-go pull requests for the Language and Compiler, Performance, and Infrastructure sections. No specific file, test, or entry point is named, and completion is represented by progress across the listed release-plan items rather than one independently defined change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- release
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100