You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Reacted by Roman, João Ferreira, Valentin Semirulnik, Kirk Waiblinger, Tobbe Lundberg, lin72h, Luke Deen Taylor, Nicolas Stepien, Zak Nesler, Matt Garrett and 32 more
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.
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.
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.
Reacted by Nicolas Stepien, Ítalo Masserano, João Ferreira and Nik
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.
Reacted by Roman, Kirk Waiblinger, João Ferreira, Daniel Rosenwasser, Oleksandr Tarasiuk and Madeline Gurriarán
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.
Reacted by Kirk Waiblinger, Roman, João Ferreira, Daniel Rosenwasser, Oleksandr Tarasiuk and Christian Svensson
Due to a lot of infrastructure issues, we'll be at least a few days late on beta.
Reacted by Luke Ramus, pravin-adhav-qp, João Dias, Vishal Kumar, Akam Foad, João Ferreira, Sacha Stafyniak, Boris, Yusuke Yamada, Mira Šerý and 26 more
Reacted by n028, Seanitzel(Sean Ray Dvir), liam, Max, Stav Alfi, João Ferreira, maik-bol, rbnts, maxarvid, Alexander Kachkaev and 19 more
Reacted by Alexander Simbirtsev, Matheus Cardoso, Colin McDonnell, Uwe S., Shay Erlichmen and 20170922
Reacted by Samuel Painchaud, Sam Glendenning, Tomasz Didyk, Ashley Claymore, Joe DeMatteo, Alexander J. Vincent, n028, Owen Buckley, Brian Jenkins, Oleg Kislitsyn and 30 more
Reacted by Alexander Kachkaev, Tyler Smith, lin72h, Tetsuya Morimoto, Brett Zamir, XiaoYan Li, kh4f, Divyesh Bhandari, Akihiro Nagai, René Herrmann and 15 more
Reacted by Owen Buckley, João Ferreira, Mattias Strömdahl, Jason Miller and Sacha Stafyniak
Nathan Shively-Sanders (@sandersn) once watched me struggle to write a @typedef tag in JSDoc and said it was like watching a comedy routine. Maybe this is my next bit.
Activity
dasa commentedon Jul 31, 2026
2027, is that a typo?
DanielRosenwasser commentedon Jul 31, 2026
Sure is! 🫠🤦♂️
[core] Depend on @typescript/typescript6 instead of pinning
[core] Depend on @typescript/typescript6 instead of pinning
DanielRosenwasser commentedon Sep 1, 2026
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.
Flarette commentedon Sep 3, 2026
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.
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.
jakebailey commentedon Sep 3, 2026
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
Flarette commentedon Sep 3, 2026
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 resourceThis 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.
RyanCavanaugh commentedon Sep 4, 2026
Users don't decide how their dependencies' declaration files are written. It's a very bad experience if you install
supercool-liband 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.RyanCavanaugh commentedon Sep 4, 2026
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.
stavalfi-oasis commentedon Sep 5, 2026
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)
jakebailey commentedon Sep 5, 2026
Please file an issue if you have something that reproduces.
2 remaining items
DanielRosenwasser commentedon Oct 5, 2026
Due to a lot of infrastructure issues, we'll be at least a few days late on beta.
DanielRosenwasser commentedon Oct 14, 2026
TypeScript Bot (@typescript-bot) create release-7.1
DanielRosenwasser commentedon Oct 14, 2026
*more loudly and audibly annoyed* I said, TypeScript Bot (@typescript-bot) create release-7.1
DanielRosenwasser commentedon Oct 14, 2026
TypeScript Bot (@typescript-bot) create release-7.1
DanielRosenwasser commentedon Oct 15, 2026
TypeScript Bot (@typescript-bot) create release-7.1
typescript-automation commentedon Oct 15, 2026
Starting jobs; this comment will be updated as builds start and complete.
create release-7.1DanielRosenwasser commentedon Oct 15, 2026
Nathan Shively-Sanders (@sandersn) once watched me struggle to write a
@typedeftag in JSDoc and said it was like watching a comedy routine. Maybe this is my next bit.DanielRosenwasser commentedon Oct 15, 2026
TypeScript Bot (@typescript-bot) create release-7.1
DanielRosenwasser commentedon Oct 16, 2026
TypeScript Bot (@typescript-bot) create release-7.1
typescript-automation commentedon Oct 16, 2026
Starting jobs; this comment will be updated as builds start and complete.
create release-7.1typescript-automation commentedon Oct 16, 2026
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
Waldenesque commentedon Oct 16, 2026
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!!
DanielRosenwasser commentedon Oct 16, 2026
DanielRosenwasser commentedon Oct 16, 2026
TypeScript Bot (@typescript-bot) create release-7.1
typescript-automation commentedon Oct 16, 2026
Starting jobs; this comment will be updated as builds start and complete.
create release-7.1