The parallel improvement of the brand new language server and extension ensured that by late 2025 it was attainable for VS Code improvement 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 crew and used to prioritize improvement.
Because the platform advanced, the use instances for the VS Code crew modified. By early 2026 TypeScript 7 was steady and practically feature-complete, so the crew 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 velocity up. As soon as that course of was examined and dealing, they might change all improvement to TypeScript 7.
Having such an enormous mission tackle TypeScript 7 early reaped large 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 converse for themselves. Kind checking all the VS Code codebase is now 7x sooner, with most extensions checked in beneath a second. The one exception was GitHub Copilot, which is sort of as large because the editor itself, which kind checked in 2.5 seconds.
