TypeScript 6.0 RC
devblogs.microsoft.com
TypeScript 6.0 RC
1–10 of 52 posts
Re: TypeScript 6.0 RC
#2Though TypeScript 7.0 will be significant in that it will use the new Go compiler
Re: TypeScript 6.0 RC
#3On the other hand, I can understand leaving it as the last thing to do, after the foundation has set. Also, the TypeScript team has really done an amazing job all these years with backward compatibility, so that is extremely reassuring.
Maybe my uneasiness is just impatience to get to use the sped-up version in my app as well! :)
Re: TypeScript 6.0 RC
#4Re: TypeScript 6.0 RC
#5I would still have a full head of hair if this had been the case since the beginning. Nonetheless I am glad that we got here in the end.
Re: TypeScript 6.0 RC
#6> strict is now true by default I would still have a full head of hair if this had been the case since the beginning. Nonetheless I am glad that we got here in the end.
Re: TypeScript 6.0 RC
#7As a user, I'm of course very excited about v7. As a developer of an app that _integrates_ TypeScript, however, I feel a bit uneasy seeing the API feature still marked as "not ready" on the roadmap. On the other hand, I can understand leaving it as the last thing to do, after the foundation has set. Also, the TypeScript team has really done an amazing job all these years with backward compatibility, so that is extrem…
Re: TypeScript 6.0 RC
#8> strict is now true by default I would still have a full head of hair if this had been the case since the beginning. Nonetheless I am glad that we got here in the end.
Re: TypeScript 6.0 RC
#9As a user, I'm of course very excited about v7. As a developer of an app that _integrates_ TypeScript, however, I feel a bit uneasy seeing the API feature still marked as "not ready" on the roadmap. On the other hand, I can understand leaving it as the last thing to do, after the foundation has set. Also, the TypeScript team has really done an amazing job all these years with backward compatibility, so that is extrem…
FWIW I tried it with the VSCode preview in two monorepos we have - one frontend and one backend GraphQL servers with complex types - absolutely no issues (except one breaking change in tsconfig with baseUrl being removed) and fast compile times.
The moduleResolution: node deprecation is the one I'd flag for anyone not paying attention yet. Switching to nodenext forced us to add .js extensions to all
relative imports, which was a bigger migration than expected.
Compilation speed improvement is real though. Noticeably faster on incremental builds.Re: TypeScript 6.0 RC
#10> strict is now true by default I would still have a full head of hair if this had been the case since the beginning. Nonetheless I am glad that we got here in the end.
I came to point that out too. What an awesome development. I think this will have a meaningful impact on the general quality of TS projects over the coming years.