Repository navigation
TypeScript 5.0 Iteration Plan #51362
Description
This document outlines our focused tasks for TypeScript 5.0. It minimally indicates intent to investigate tasks or contribute to an implementation. Nothing is set in stone, but we will strive to complete these tasks in a reasonable timeframe.
| Date | Event |
|---|---|
| November 15th | TypeScript 4.9 Release |
| January 20th | Create 5.0 Beta (5.0.0) Build for Testing |
| January 24th | TypeScript 5.0 Beta Release |
| February 24th | Create 5.0 RC (5.0.1) Build for Testing |
| February 28th | TypeScript 5.0 RC Release |
| March 10th | Create 5.0 Final (5.0.2) Build for Testing |
| March 16th | TypeScript 5.0 Final Release 🚀 |
gantt
dateFormat YYYY-MM-DD
TypeScript 4.9 Stabilization Period : 2022-10-28, 2022-11-11
TypeScript 5.0 Beta Development : 2022-10-28, 2023-01-19
TypeScript 5.0 RC Development : 2023-01-19, 2023-02-24
TypeScript 5.0 Stabilization Period : 2023-02-24, 2023-03-16
todayMarker stroke-width:5px,stroke:#0f0,opacity:0.5
Language and Compiler Features
- ECMAScript Decorators
- Unify All
enums as Unions - Legacy Flag Deprecation
- Investigate Bundler-Oriented Module Resolution Options
- Support
.tsas a Module Specifier for Bundler/Loader Scenarios - Declaration Files for Non-JavaScript Files
- Allow Arrays in
extendsfortsconfig.jsonFiles - Investigate Per-File Settings
lib.d.tsUpdates- Make
@types/webVersionable
Editor Productivity
switch/caseSnippet Completions- Investigate
SharedArrayBuffer-Backed Host for Web Editing Contexts - Investigate Limited ATA-Like Scenarios in Web Editing Contexts
- Implement Cancellation in Web Editing Contexts
- Easy Run/Debug for Loose TypeScript Files
Performance
- Investigate Module Resolution Caching in
.tsbuildinfoFiles - Optimizing
.tsbuildinfo - Investigate Tooling for JIT Deoptimizations
Activity
DanielRosenwasser commentedon Nov 1, 2022
The 4.9 iteration plan is over at #50457.
akononenko-sumo commentedon Nov 2, 2022
It's so sad that adding proper type support for
throwis not on the roadmap for v5...MLoughry commentedon Nov 2, 2022
One idea I had previously floated to Andrew Casey (@amcasey) was to add compiler/server APIs with asynchronous signatures in 5.0 (even if they're still synchronous under the hood), and deprecate the synchronous APIs. This would allow Typescript to later (6.0?) remove the synchronous APIs and unblock the ability to perform asynchronous I/O (or even worker-based parallelization?) in future versions.
lukeapage commentedon Nov 6, 2022
I’d love to see the core team engage with issues that are for example 400+ thumbs up and marked “awaiting feedback” rather than issues that seem less important.
Even if the answer is that the team consider it to not be typescript’s responsibility and close the issue - i would rather that than limbo and newer but less important features being tackled.
https://github.com/microsoft/TypeScript/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc+label%3A%22Awaiting+More+Feedback%22
patroza commentedon Nov 11, 2022
Luke Page (@lukeapage) I smell another 400+ thumbs up incoming..
kuator commentedon Nov 27, 2022
Waiting for any news on LSP implementation
3xau1o commentedon Dec 4, 2022
Any plan to add experimental support ECMAScript Operator Overloading, Pipeline Operator or extension methods?
ljharb commentedon Dec 4, 2022
@mindlid It would be highly inappropriate to add support for any proposal prior to stage 3.
3xau1o commentedon Dec 4, 2022
ljharb commentedon Dec 4, 2022
3xau1o commentedon Dec 4, 2022
ljharb commentedon Dec 4, 2022
3xau1o commentedon Dec 5, 2022
47 remaining items
typescript-bot commentedon Mar 10, 2023
Heya Daniel Rosenwasser (@DanielRosenwasser), I've started to update the version number on
release-5.0to5.0.2for you. Here's the link to my best guess at the log.SmashingQuasar commentedon Mar 13, 2023
Again, deprecations should not break existing code. That is the whole concept of a deprecation. If they are breaking existing code, they are not deprecations, they are feature removal with a retro-compatibility bridge. If they are handled that way, then sure, those are breaking changes that constitute a major version. They should however be listed as such and not as deprecations.
DanielRosenwasser commentedon Mar 13, 2023
We're having an issue with a build pipeline, so we'll be targeting the stable release for Thursday, March 16th.
trim21 commentedon Mar 13, 2023
DanielRosenwasser commentedon Mar 13, 2023
Ugh, that is a typo in the release plans. 5.0.2 is the release I'm talking about. I've fixed up the original comment.
sacummings91 commentedon Mar 15, 2023
It's crazy that people have the nerve to come in here and complain. TS is literally free for us to use and everyone on the team puts a massive amount of effort into it. You should just be grateful it exists.
jez9999 commentedon Mar 16, 2023
It's the 16th... any chance of TS5 today?
RyanCavanaugh commentedon Mar 16, 2023
Yes! https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/
3xau1o commentedon Mar 17, 2023
@polkovnikov-ph https://civet.dev/ supports ES proposals and compiles to typescript
DanielRosenwasser commentedon Mar 30, 2023
TypeScript Bot (@typescript-bot) bump release-5.0
typescript-bot commentedon Mar 30, 2023
Heya Daniel Rosenwasser (@DanielRosenwasser), I've started to update the version number on
release-5.0to5.0.3for you. Here's the link to my best guess at the log.DanielRosenwasser commentedon Apr 5, 2023
TypeScript Bot (@typescript-bot) bump release-5.0
typescript-bot commentedon Apr 5, 2023
Heya Daniel Rosenwasser (@DanielRosenwasser), I've started to update the version number on
release-5.0to5.0.4for you. Here's the link to my best guess at the log.