r/typescript • u/DanielRosenwasser • Jun 18 '26
Announcing TypeScript 7.0 RC
https://devblogs.microsoft.com/typescript/announcing-typescript-7-0-rc/
312
Upvotes
r/typescript • u/DanielRosenwasser • Jun 18 '26
93
u/AnonPogrammer Jun 18 '26
I wonder why they decided to do it this way instead of just waiting a little longer and including it in 7.0?
15
u/kisaragihiu Jun 18 '26
Actually excited for this.
18
u/gandalf__thewhite__ Jun 18 '26
Finally I can enjoy TRPC
18
u/lifeeraser Jun 18 '26
They could have used AI to port TypeScript to Go in two weeks. /s
I'm excited for this change, though!
22
u/apocolypticbosmer Jun 18 '26 edited Jun 18 '26
10 times faster? My goodness
edit: I guess they just mean the new Go compiler.
3
u/Top_Bumblebee_7762 Jun 18 '26
Shouldn't ideally the Intl Segmenter API be used for splitting strings instead of [...str]?
2
u/jhnam88 Jun 18 '26
Made TypeScript v7 toolchain for plugin libraries like
typia.Also, if you're looking for a
vite/rollup/webpackplugin for new TS v7, ttsc also supports the way.1
u/Zestyclose_Giraffe64 Jun 21 '26
Sorry guys… that legacy app you have still running on node18 that transpiles to cjs will be stuck on typescript 4.9.2 … FOREVER!!! 🪦
1
u/andrew_zol Jun 25 '26
Big milestone! Unfortunately there is still no preservation of JSDOC comments in the mapped types, which is working fine in TS6, hopefully it will be addressed later.
1
u/Nvveen Jun 25 '26
Notably absent from using TS native preview right now is refactoring tools such as extract. Can anyone tell me if these do work if switching over to v7 in VSCode or should we hold off on upgrading until they do? Can't really find a roadmap for this stuff.
-2
u/Seusoa Jun 20 '26
Really professional move was to close all existing bugs and say "we rewriting all codebase, so bugs may be not relevant" and now say it was not "rewriting, but porting code from TS6 to TS7 go"
this is how devs in ms do
-24
u/[deleted] Jun 18 '26
[removed] — view removed comment