Skip to content

TypeScript 5.9 Iteration Plan #61648

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
DanielRosenwasser opened this issue May 2, 2025 · 3 comments
Open

TypeScript 5.9 Iteration Plan #61648

DanielRosenwasser opened this issue May 2, 2025 · 3 comments
Labels
Planning Iteration plans and roadmapping

Comments

@DanielRosenwasser
Copy link
Member

Date Event
2024-02-25 TypeScript 5.8 Release
2024-05-23 Create 5.9 Beta (5.9.0) Build for Testing
2024-05-26 TypeScript 5.9 Beta Release
2024-06-13 Create 5.9 RC (5.9.1) Build for Testing
2024-06-17 TypeScript 5.9 RC Release
2024-07-18 Create 5.9 Final (5.9.2) Build for Testing
2024-07-22 TypeScript 5.9 Final Release 🚀

Compiler and Language

Editor and Language Service

Performance

@DanielRosenwasser DanielRosenwasser pinned this issue May 2, 2025
@DanielRosenwasser DanielRosenwasser added the Planning Iteration plans and roadmapping label May 2, 2025
@controversial
Copy link

Is the “Checked Returns for Conditional and Indexed Access Types” feature (originally #56941, now #61359) planned to re-land in 5.9?

(this feature was included in 5.8 beta, but reverted before the RC; @gabritto had mentioned the feature could re-land in 5.9)

@DanielRosenwasser
Copy link
Member Author

We're not planning on bringing that in for 5.9. We want to be more conservative about larger features that are more involved while so much of our attention is currently on the port.

@controversial
Copy link

controversial commented May 5, 2025

understood, thanks for clarifying @DanielRosenwasser

should we expect that that feature (or others of similar scope) won’t land in Typescript until 7.x?

i.e. should we expect it will never land in Strada—in order to avoid the additional development burden of trying to port a “moving target”—but instead the team will hold off until Corsa is ready to be the target of new features like this one?

(to be clear, that approach would not be at all unreasonable to me, just curious what to expect!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Planning Iteration plans and roadmapping
Projects
None yet
Development

No branches or pull requests

2 participants