TypeScript 6.0 RC is here with tighter type checks for function expressions in generic calls. It even covers generic JSX, and Microsoft nods to a Go-based TypeScript 7.0 for speed.
TypeScript RC 6.0: Stricter checks in generic calls
The release candidate tightens how function expressions are typed when used inside generic calls, including generic JSX. This reduces subtle bugs caused by inference in nested generic contexts. Teams may discover that some generic calls require an explicit type argument to satisfy the new checks, especially in complex component trees that span large RC-era projects.
Go-based TypeScript 7.0 trajectory and RC harmony
Microsoft moves toward a Go-based 7.0 for the compiler and language service, aiming for speed gains on large repos. The plan preserves backward compatibility while enabling faster migration feedback. Expect a staged transition rather than a sudden cliff, with careful guidance for teams chasing 6.0 RC live projects in 2026.
RegExp.escape in es2025 and dom typings consolidation
The RC includes RegExp.escape in the es2025 library, a pragmatic helper for escaping regex characters such as *, ?, and +. With this, patterns stay readable and less error prone. lib.dom.d.ts now consolidates dom.iterable and dom.asynciterable into a single lib.dom.d.ts, simplifying typings across DOM APIs.
Import assertions and deprecation extensions
Microsoft extends the deprecation of import assertion syntax to import calls. Code that uses an assert pattern will be treated with caution. The direction leans toward import attributes rather than asserts, nudging developers toward with style patterns in 2026.
Deprecations and asserts keyword evolution
The asserts keyword drifted into earlier proposals, but the path forward embraces import attributes. Expect migration tips that show when to add explicit type arguments in generic calls and when to pivot to newer patterns as part of a 6.0 RC migration plan in 2026.
Installation tips and migration planning
To preview the RC, run npm install -D typescript@rc. The notes emphasize migration guidance, testing for generic JSX, and keeping dependencies aligned with dom typings. For large codebases, plan incremental updates to surface edge cases early in 2026.
What to expect next: The Go-based engine and 7.0 horizon
The Go-based engine behind TypeScript 7.0 promises a faster compiler and smoother editor integration. Adoption will be staged to minimize disruption, with feedback loops designed to catch migration issues. The bottom line: 7.0 aims for better performance while staying compatible with 6.0 RC patterns in 2026.
Final reflections and practical takeaways
In short, TypeScript 6.0 RC marks a careful but confident step forward. Stricter generic checks, RegExp.escape, and the dom typings consolidation reduce surprises and improve reliability. TypeScript teams relying on generic JSX and advanced DOM features will likely enjoy fewer bugs and a clearer migration story in 2026.
If you’re responsible for a team, the RC offers a valuable early look at the future. TypeScript and RC appear together on the roadmap, signaling a cohesive direction for the language as runtime environments evolve in 2026.
Original article: https://www.infoworld.com/article/4143186/typescript-6-0-reaches-release-candidate-stage.html
Have thoughts? Please share them in the comments to kick off a friendly discussion.
FAQ: TypeScript 6.0 RC and migration
- What is the practical impact of the stricter checks in 6.0 RC? It improves reliability by catching ambiguous generic calls early.
- Will there be explicit type arguments required? In some complex cases, yes; you can provide them to satisfy the new checks.
- Is RegExp.escape available in es2025? Yes, it’s included in es2025, per the ECMAScript proposal.
- When will TypeScript 7.0 ship? The plan is to release after 6.0 RC with a Go-based engine; expect staged migration over months.
References
- InfoWorld: TypeScript 6.0 RC release candidate
- TypeScript Blog
- MDN: RegExp.escape
- ECMAScript RegExp.escape proposal