The parallel improvement of the brand new language server and extension ensured that by late 2025 it was potential for VS Code improvement to shift to TypeScript 7, with TypeScript 6 used as a fallback if there have been any points. These instances might then be reported again to the TypeScript group and used to prioritize improvement.
Because the platform developed, the use instances for the VS Code group modified. By early 2026 TypeScript 7 was secure and practically 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 may swap all improvement to TypeScript 7.
Having such a giant venture 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 useful suggestions. The outcomes converse for themselves. Kind checking your complete VS Code codebase is now 7x quicker, with most extensions checked in below 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.
