TypeScript 7.1 Iteration Plan

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 type On Import Attributes
Investigate Node 26 Package Maps
Add es2026 option for lib and target
Support Source Phase Imports
lib.d.ts Updates for New Iterator Methods
Promise.allKeyed and Promise.allSettledKeyed
lib.d.ts Updates 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

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

2027, is that a typo?

Sure is! 🫠🤦‍♂️

[core] Depend on @typescript/typescript6 instead of pinning

For anyone following along - we're thinking we want a bit more time to make sure we get testing on the API, and we don't want a lot of churn following the beta. So we are looking at pushing out the beta about 2 weeks further. Details to come on what that means for the RC and final release dates too.

Glad to see all the performance improvements!
Speaking of which, does the team plan to revisit the instantiation depth limits and similar errors in the tsgo compiler? These numbers were chosen arbitrarily for the tsc performance target and the original reasoning is no longer applicable.

if c.instantiationDepth == 100 || c.instantiationCount >= 5_000_000 {
    // ...
    c.error(... Type_instantiation_is_excessively_deep_and_possibly_infinite)
}

The ecosystem has been moving to ever increasing instantiation count in the pursuit of the e2e type safety. With StandartShema validation libraries like zod providing the foundation and typed api clients\metaframeworks extending the chain all the way to the frontend. Once generics\discriminants are thrown into the mix there are legitimate cases where old limits become a bottleneck.

We have no plans to change these limits. It would be a shame to make the compiler fast only to increase depths and go slow again.

See also: microsoft/typescript-go#1637

We have no plans to change these limits. It would be a shame to make the compiler fast only to increase depths and go slow again.

See also: microsoft/typescript-go#1637

The Jevons paradox is phenomenon when technological improvements that increase the efficiency of a resource's use lead to a rise, rather than a fall, in total consumption of that resource

This has always been the trajectory of the compute innovation. We don't use improved efficiency just to run our Nokia's for a year on a single charge, we run liquid glass instead.

The old limits don't make deep instantiation run faster, they just prevent it from running at all! Considering that the rise of limits doesn't even impact projects that don't cross them, i don't see the reason why it can't be at least a compiler flag.

This policy reads extremely backwards to the spirit of progress and innovation. Let users decide if they want speed or capability.

Let users decide if they want speed or capability.

Users don't decide how their dependencies' declaration files are written. It's a very bad experience if you install supercool-lib and it wildly misbehaves in unpredictable ways because it depends on extremely deep instantiation, which you then have to turn on everywhere and slow down all your other inference.

I should also add - one of the goals of content mappers is that you can move a lot of this hypercomplex meta-programming type inference stuff into a static process that produces a much, much faster static .d.ts file. The projects writing SQL/GraphQL/etc parsers in the type system should be looking into this.

great work thank you!! are you also planning to fix all memory leaks? latest version gets to 30-40+ GB RAM quite often (from vscode)

Please file an issue if you have something that reproduces.

Starting jobs; this comment will be updated as builds start and complete.

Command	Status	Results
`create release-7.1`	✅ Started	❌ Results

Daniel Rosenwasser (@DanielRosenwasser)

Hey, Daniel Rosenwasser (@DanielRosenwasser)! I was unable to create the new release branch.

Check the logs at: https://github.com/microsoft/TypeScript/actions/runs/38827102383

Try these on. Put these on.

I'm givin you a choice: either put on these glasses, or start eatin that trash can!

Put on the glasses. Take a look! Put em on.

Put the glasses on! Put em on!

Look! Look at em, they're everywhere!!

TypeScript Bot (@typescript-bot)

TypeScript Bot (@typescript-bot) create release-7.1

Starting jobs; this comment will be updated as builds start and complete.

Command	Status	Results
`create release-7.1`	✅ Started	✅ Results

Daniel Rosenwasser (@DanielRosenwasser)

Hey, Daniel Rosenwasser (@DanielRosenwasser)! I've created release-7.1 with version 7.1.0-beta for you.

This must be that agentic coding thing everyone's been talking about.

Can we expect beta blogpost soon?

Yes, hopefully tomorrow. Sorry everyone!

TypeScript Bot (@typescript-bot)

TypeScript Bot (@typescript-bot) sync release-7.1

Starting jobs; this comment will be updated as builds start and complete.

Command	Status	Results
`sync release-7.1`	✅ Started	✅ Results

Daniel Rosenwasser (@DanielRosenwasser)

Hey, Daniel Rosenwasser (@DanielRosenwasser)! I've pulled main into release-7.1 for you.

The automation messages indicate that release-7.1 was created with version 7.1.0-beta and synced with main, but there are no corresponding artifacts on npm or GitHub Releases.

When will the beta be published? Or are we expected to build it from the release-7.1 branch?

Thanks for your patience everyone!

The beta is now published, and the blog post is up here. The v7.1-beta tag has also been created.

Navigation Menu

Repository navigation

TypeScript 7.1 Iteration Plan #63703

Language and Compiler

Editor Productivity

Performance

Infrastructure

Website

11 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

TypeScript 7.1 Iteration Plan #63703

Description

Language and Compiler

Editor Productivity

Performance

Infrastructure

Website

Activity

dasa commented on Jul 31, 2026

DanielRosenwasser commented on Jul 31, 2026

DanielRosenwasser commented on Sep 1, 2026

Flarette commented on Sep 3, 2026

jakebailey commented on Sep 3, 2026

Flarette commented on Sep 3, 2026

RyanCavanaugh commented on Sep 4, 2026

RyanCavanaugh commented on Sep 4, 2026

stavalfi-oasis commented on Sep 5, 2026

jakebailey commented on Sep 5, 2026

11 remaining items

typescript-automation commented on Oct 16, 2026

typescript-automation commented on Oct 16, 2026

Waldenesque commented on Oct 16, 2026

DanielRosenwasser commented on Oct 16, 2026

DanielRosenwasser commented on Oct 16, 2026

typescript-automation commented on Oct 16, 2026

typescript-automation commented on Oct 16, 2026

DanielRosenwasser commented on Oct 16, 2026

Smrtnyk commented on Oct 16, 2026

DanielRosenwasser commented on Oct 19, 2026

DanielRosenwasser commented on Oct 19, 2026

typescript-automation commented on Oct 19, 2026

typescript-automation commented on Oct 19, 2026

erlichmen commented on Oct 20, 2026

DanielRosenwasser commented on Oct 20, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions