{"id":5246,"date":"2026-07-08T07:58:29","date_gmt":"2026-07-08T15:58:29","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/typescript\/?p=5246"},"modified":"2026-07-08T07:58:29","modified_gmt":"2026-07-08T15:58:29","slug":"announcing-typescript-7-0","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/typescript\/announcing-typescript-7-0\/","title":{"rendered":"Announcing TypeScript 7.0"},"content":{"rendered":"

Today we are proud to announce the availability of TypeScript 7, a 10x faster native port of TypeScript!<\/p>\n

Since its early days, TypeScript has promised to deliver on JavaScript that scales.\nBy bringing strong type-checking and rich tooling to the world of JavaScript, TypeScript made it possible to build non-trivial high-quality apps across platforms.<\/p>\n

Last year, our team unveiled TypeScript’s next step<\/a> in scaling: making every part of the toolset an order of magnitude faster.\nThe mission was a native port of TypeScript built in Go that could make the most of modern hardware.\nThis port was done as faithfully as possible, writing new code while maintaining the structure and logic of the original codebase to keep results consistent and compatible between the two compilers.\nThe key difference is that with this new codebase, TypeScript 7 brings native code speed, shared memory multithreading, and a number of new optimizations that typically yield speedups between 8x and 12x on full builds.<\/p>\n

Just as with any other release, TypeScript 7 is available via npm:<\/p>\n

npm install -D typescript\r\n<\/code><\/pre>\n
That will get you the new tsc<\/code> executable in your workspace (which you can run via npx tsc<\/code>).\nOf course, a big part of the TypeScript experience is also about editor support.\nYour favorite code editor should easily support TypeScript 7 with its new support for the language server protocol (LSP), and its new speed and multithreading improvements.\nWhether you’re using something like VS Code, Visual Studio, WebStorm, or any other modern editor, TypeScript 7 should work great.\nJust check your editor’s documentation – for example, VS Code has a dedicated extension for TypeScript 7 that you can use today<\/a>, and Visual Studio will automatically enable TypeScript 7 based on your workspace.<\/p>\n
What Does A Faster TypeScript Mean?<\/h2>\n
A faster TypeScript sounds great on paper, but what does it mean in practice?\nMaybe it helps to think about where TypeScript comes up at every stage of development.<\/p>\n
A typical day of development might involve opening your editor, opening a TypeScript file, and running an operation like find-all-references<\/em> across your projects.\nThen as you’d start to make edits, maybe you’d expect auto-completions to pop up, and get red squiggles on the fly as you’d make edits.\nWhen you (and more recently, perhaps an AI agent) were ready to build your project, you’d run tsc<\/code>, check the output for errors, and then run your generated code somehow.<\/p>\n
A faster TypeScript means every part above is streamlined.\nWaiting for your editor to fully load your project will feel instantaneous.\nDelays on find-all-references<\/em>, auto-completion, and diagnostics should take a fraction of the time they used to.\nAnd when you run tsc<\/code>, maybe in --watch<\/code> mode, you’ll be able to tighten your feedback loop and iterate faster than ever before.<\/p>\n
You can see this on real-world projects.\nIn fact, you can try comparing on a few open-source projects yourself.\nHere are the build times of running TypeScript 6 and 7 on some fairly large open source codebases.<\/p>\n\n\n\n\n\n\n\n\n\n
Codebase<\/th>\nTypeScript 6<\/th>\nTypeScript 7<\/th>\nSpeedup<\/th>\n<\/tr>\n<\/thead>\n
vscode<\/td>\n125.7s<\/td>\n10.6s<\/td>\n11.9x<\/td>\n<\/tr>\n
sentry<\/td>\n139.8s<\/td>\n15.7s<\/td>\n8.9x<\/td>\n<\/tr>\n
bluesky<\/td>\n24.3s<\/td>\n2.8s<\/td>\n8.7x<\/td>\n<\/tr>\n
playwright<\/td>\n12.8s<\/td>\n1.47s<\/td>\n8.7x<\/td>\n<\/tr>\n
tldraw<\/td>\n11.2s<\/td>\n1.46s<\/td>\n7.7x<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
\"Compile<\/p>\n
TypeScript 7 also typically does better while asking for less<\/em> aggregate memory over the span of a build.<\/p>\n\n\n\n\n\n\n\n\n\n
Codebase<\/th>\nTypeScript 6<\/th>\nTypeScript 7<\/th>\nMemory Delta<\/th>\n<\/tr>\n<\/thead>\n
vscode<\/td>\n5.2GB<\/td>\n4.2GB<\/td>\n-18%<\/td>\n<\/tr>\n
sentry<\/td>\n4.9GB<\/td>\n4.6GB<\/td>\n-6%<\/td>\n<\/tr>\n
bluesky<\/td>\n1.8GB<\/td>\n1.3GB<\/td>\n-26%<\/td>\n<\/tr>\n
playwright<\/td>\n1.0GB<\/td>\n0.9GB<\/td>\n-11%<\/td>\n<\/tr>\n
tldraw<\/td>\n0.6GB<\/td>\n0.5GB<\/td>\n-15%<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
\"Differences<\/p>\n
Of course, there’s more to the experience than the full build.\nOn the same computer, opening a file with an error in the VS Code codebase would previously take about 17.5 seconds from the time you opened the editor to the time you saw the first error.\nWith TypeScript 7, it’s under 1.3 seconds – over 13x faster.<\/p>\n
Battle-Tested and Ready for Production<\/h2>\n
The TypeScript project contains tens of thousands of tests built over more than a decade that run on every commit on our main<\/code> branch.\nThey’ve ensured every one of our releases is stable and reliable.<\/p>\n
But TypeScript 7 is no ordinary release.\nBeyond our test suite, we’ve leveraged a number of different resources to make sure TypeScript 7 is solid for production use.<\/p>\n
Over the last year we’ve worked with many large teams internally and externally to test TypeScript 7 on real-world codebases.\nThe results have been overwhelmingly positive, with entire companies reporting that TypeScript 7 has been stable, fast, and easy to adopt.\nFor example, the VS Code team recently highlighted their experience with TypeScript 7’s preview releases<\/a> to move faster in their development cycle.\nWe’ve also worked with Microsoft teams like Loop, Office, PowerBI, Teams, and Xbox to ensure that TypeScript is ready for the largest of codebases.\nLikewise, companies like Bloomberg, Canva, Figma, Google, Lattice, Linear, Miro, Notion, Sentry, Slack, Vanta, Vercel, VoidZero, and more have worked with us to test TypeScript 7 on their codebases and given us feedback to make it better.<\/p>\n
Additionally, we’ve rebuilt much of our broader test infrastructure to run on TypeScript 7.\nTypeScript 6 and earlier had automated and on-demand testing for TypeScript and JavaScript projects on GitHub to detect regressions in the compiler and language service.\nThe same testing is back, and running against TypeScript 7, finding issues in real codebases so we can find gaps in our core test suite and ship a better experience.<\/p>\n
The combination of explicit feedback, automated crash reports, and aggressive testing has made a measurable difference in quality.\nIn fact, our data insights have shown us that TypeScript 7.0’s new language server has actually reduced failing language server commands by over 80%, and reduced server crashes by over 60% compared to that of TypeScript 6.0.<\/p>\n
We’ve also heard some incredible feedback from teams at scale:<\/p>\n