The parallel growth of the brand new language server and extension ensured that by late 2025 it was doable for VS Code growth to shift to TypeScript 7, with TypeScript 6 used as a fallback if there have been any points. These instances may then be reported again to the TypeScript group and used to prioritize growth.
Because the platform developed, the use instances for the VS Code group modified. By early 2026 TypeScript 7 was steady and almost feature-complete, so the group started to make use of it to construct all of their very own built-in extensions. This allowed them to rethink their toolchain, altering the bundler from webpack to the one constructed into esbuild, giving them one other pace up. As soon as that course of was examined and dealing, they might swap all growth to TypeScript 7.
Having such a giant challenge tackle TypeScript 7 early reaped massive rewards, because the ensuing virtuous cycle allowed each VS Code and TypeScript to maneuver ahead collectively, fixing points as they arose and offering worthwhile suggestions. The outcomes communicate for themselves. Sort checking your complete VS Code codebase is now 7x quicker, with most extensions checked in beneath a second. The one exception was GitHub Copilot, which is nearly as massive because the editor itself, which kind checked in 2.5 seconds.