Microsoft Developer Blogs
devblogs.microsoft.com › dev blogs › typescript › a 10x faster typescript
A 10x Faster TypeScript - TypeScript
March 11, 2025 - Embarking on a native port of the existing TypeScript compiler and toolset to achieve a 10x performance speed-up.
GitHub
github.com › microsoft › Typescript › wiki › Performance
Performance · microsoft/TypeScript Wiki · GitHub
However, if we know enough about List<T>, we can reduce this assignability check to determining whether Dog is assignable to Animal (i.e. without considering each member of List<T>). (In particular, we need to know the variance of the type parameter T.) The compiler can only take full advantage of this potential speedup if the strictFunctionTypes flag is enabled (otherwise, it uses the slower, but more lenient, structural check). For this reason, we recommend building with --strictFunctionTypes (which is enabled by default under --strict). TypeScript compilation is often performed with other build tools in mind - especially when writing web apps that might involve a bundler.
Author microsoft
A 10x Faster TypeScript
(Hi, dev lead of TypeScript here) Lots of questions about why Go in thread, let me address. We definitely knew when choosing Go that there were going to be people questioning why we didn't choose Rust (or others). It's a good question because Rust is an excellent language, and barring other constraints, is a strong first choice when writing new native code. Portability (i.e. the ability to make a new codebase that is algorithmically similar to the current one) was always a key constraint here as we thought about how to do this. We tried tons of approaches to get to a representation that would have made that port approach tractable in Rust, but all of them either had unacceptable trade-offs (perf, ergonomics, etc.) or devolved in to "write your own GC"-style strategies. Some of them came close, but often required dropping into lots of unsafe code, and there just didn't seem to be many combinations of primitives in Rust that allow for an ergonomic port of JavaScript code (which is pretty unsurprising when phrased that way - most languages don't prioritize making it easy to port from JavaScript/TypeScript!). In the end we had two options - do a complete from-scrach rewrite in Rust, which could take years and yield an incompatible version of TypeScript that no one could actually use, or just do a port in Go and get something usable in a year or so and have something that's extremely compatible in terms of semantics and extremely competitive in terms of performance. And it's not even super clear what the upside of doing that would be (apart from not having to deal with so many "Why didn't you choose Rust?" questions). We still want a highly-separated API surface to keep our implementation options open, so Go's interop shortcomings aren't particularly relevant. Go has excellent code generation and excellent data representation, just like Rust. Go has excellent concurrency primitives, just like Rust. Single-core performance is within the margin of error. And while there might be a few performance wins to be had by using unsafe code in Go, we have gotten excellent performance and memory usage without using any unsafe primitives. In our opinion, Rust succeeds wildly at its design goals, but "is straightforward to port to Rust from this particular JavaScript codebase" is very rationally not one of its design goals. It's not one of Go's either, but in our case given the way we've written the code so far, it does turn out to be pretty good at it. More on reddit.com
329
1663
March 11, 2025Typescript performance vs JavaScript
Yes it compiles to vanilla JS. This chart is basically click bait as it's been reposted constantly but there's really no way to account for all the factors that would influence a language's net power consumption. The only reasonable justification for a difference would be the additional compute required to type check when building, but the idea that would result in a 500% total increase compared to JS is nonsense. More on reddit.com
41
0
February 1, 2024How can I speed up initial TypeScript compile times
I have a fairly big TypeScript project (200+ files) and it takes some time (10s+) to boot up when I run it in watch mode (tsc --watch). However once its going it is pretty fast to do a full typecheck More on stackoverflow.com
As TypeScript becomes 10x faster, will it become a more popular choice than Go, Java, Python and PHP for BED?
Its the compiler that gets 10x faster. Not the execution of the resulting javascript. More on reddit.com
8
0
March 12, 2025The Software House
tsh.io › blog › how-to-speed-up-your-typescript-project
How to speed up your TypeScript project? Tips & instructions
July 18, 2023 - It doesn’t sound like a lot, but with more code to come, this number will slowly increase. So what happens during TypeScript compilation? ... At this point we cannot do much with type checking, however, there is a way to speed up the compilation speed. TypeScript itself can’t change TS source code into JS files.
DEV Community
dev.to › dharamgfx › is-typescript-slower-than-javascript-the-performance-showdown-f3h
🏃♂️ Is TypeScript Slower than JavaScript? The Performance Showdown! 🕒 - DEV Community
August 29, 2024 - ... function add(a: number, b: number): number { return a + b; } // console.log(add(5)); // Error: Argument of type '5' is not assignable to parameter of type 'number' Runtime Speed: TypeScript is not slower than JavaScript at runtime.
DEV Community
dev.to › _d7eb1c1703182e3ce1782 › typescript-performance-optimization-2026-compile-speed-runtime-efficiency-and-type-safety-48ch
TypeScript Performance Optimization 2026: Compile Speed, Runtime Efficiency, and Type Safety - DEV Community
March 25, 2026 - Microsoft announced a Go-based rewrite of the TypeScript compiler targeting 10x compile speed improvements.
Architecture Weekly
architecture-weekly.com › architecture weekly › typescript migrates to go: what's really behind that 10x performance claim?
TypeScript Migrates to Go: What's Really Behind That 10x Performance Claim?
March 24, 2025 - What's actually getting faster is the TypeScript compiler, not the TypeScript language itself or the JavaScript's runtime performance. Your TypeScript code will compile faster, but it won't suddenly execute 10x faster in the browser or Node.js. ... and then clarifying that they only made the manufacturing process faster—the car itself still drives at the same speed.
Visual Studio Magazine
visualstudiomagazine.com › articles › 2026 › 07 › 08 › typescript-7-arrives-to-rock-vs-code-with-go-powered-speed.aspx
TypeScript 7 Arrives to Rock VS Code with Go-Powered Speed -- Visual Studio Magazine
3 weeks ago - TypeScript 7 is available now through the standard typescript npm package. Microsoft says full builds typically see 8x to 12x speedups.
Total TypeScript
totaltypescript.com › typescript-performance
Intro To TypeScript Performance | Total TypeScript
September 5, 2023 - It's NOT a measure of how fast your code runs. TypeScript is a compile-time tool, not a runtime tool. Simply using TypeScript will not change the speed at which the emitted JavaScript runs - TypeScript doesn't do anything at runtime.
Reddit
reddit.com › r/programming › a 10x faster typescript
r/programming on Reddit: A 10x Faster TypeScript
March 11, 2025 - But :shrug: obviously will love running the native TypeScript 7 -- looking forward to it! ... The amount of optimization that has gone into v8 is so insane. They’ve probably squeezed just about every drop of performance out of it they can. I wouldn’t ever expect a 20% runtime speed-up let alone 1000% speed-up.
Reddit
reddit.com › r/typescript › typescript performance vs javascript
r/typescript on Reddit: Typescript performance vs JavaScript
February 1, 2024 -
I recently saw a comparison of how "green" or environmentally friendly programming languages are compared to one another with a ranked list. TypeScript compared pretty poorly and was significantly worse than JavaScript. The graphic I saw was based on a study and seemed to be implying that more green meant better performance. Correct me if I am misinterpreting.
My question is why would TypeScript perform differently than JavaScript? I am not familiar with build processes due to not working with TypeScript but I would assume TS would be transpiled to JS at build time and run as vanilla JS at run time. Is this incorrect? Including a link to a post about the study below for reference in case someone can provide perspective on that.
https://www.linkedin.com/posts/bytebytego_systemdesign-coding-interviewtips-activity-7156542626446344192-nmBJ?utm_source=share&utm_medium=member_desktop
Top answer 1 of 5
56
Yes it compiles to vanilla JS. This chart is basically click bait as it's been reposted constantly but there's really no way to account for all the factors that would influence a language's net power consumption. The only reasonable justification for a difference would be the additional compute required to type check when building, but the idea that would result in a 500% total increase compared to JS is nonsense.
2 of 5
11
This study comes up every so often, but it's really not great. You can see the actual paper here (PDF warning), but please take it all with a grain of salt. If you read through that, you can see that they found a particular benchmark suite online (the "benchmarks game", which is mostly defunct at this point), and assumed that these could be used as representative samples of code in each of the different languages. They then analysed the programs via a bunch of different metrics, and explored the results. The problem is that one program written probably by one or two people to solve a very specific task makes for a very poor sample. The Typescript/Javascript divide demonstrates this very clearly. As you say, Typescript is transpiled to Javascript in a very simple way — the compiler just removes all type hints, and the result is valid Javascript. (There are a couple of exceptions to this, but these shouldn't be relevant for this topic.) Moreover, Typescript is specifically designed so that idiomatic Typescript — i.e. the style of programming that is best supported by the language — should look pretty close to idiomatic Javascript. This implies that we can generally expect Javascript and Typescript performance profiles to be very similar, as Javascript and Typescript are nearly equivalent languages. Therefore, if we see very large discrepancies between code samples from these two different languages, this should raise some very large warning flags about our data sources. In this case, I suspect the difference largely comes from people simply using two different styles of programming. Heavy uses of abstraction can reduce performance, and aggressive use of various optimisations can increase performance. It may well be that the person who wrote the Javascript samples preferred a style of programming that produced faster software, whereas the Typescript developer preferred more abstract solutions. The result is that it's very difficult to trust much of the paper's conclusions. The fact that the authors did not apply this sanity check to their own work (they treat Typescript largely as an independent language to Javascript, and do not really explore why it would be so different to Javascript in many benchmarks) suggests that they do not have a huge amount of experience with many of the languages they were benchmarking. This means they would not have been able to properly assess whether the samples were idiomatic, heavily optimised, or something else entirely. (In fairness, it's difficult to expect people to be familiar with 27 different programming languages!)
Bluebird International
bluebirdinternational.com › home › javascript vs typescript performance
JavaScript vs TypeScript Performance
June 6, 2024 - Based on these analyses, using TypeScript can improve performance in complex projects and provide better code maintainability without sacrificing execution speed.
GitConnected
levelup.gitconnected.com › speed-up-your-typescript-vscode-workflow-in-1-minute-2e3c505e008b
Speed Up TypeScript in VSCode in 1 Minute 🚀 | by Dmitry Borody | Level Up Coding
September 11, 2020 - Here’s the trick: Run a separate TypeScript process in watch mode in a terminal tab.
The Register
theregister.com › devops › 2026 › 07 › 09 › speedier-type-checks-in-typescript-70-as-first-stable-go-release-ships › 5268828
Speedier type checks in TypeScript 7.0 as first stable Go release ships
3 weeks ago - “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,” wrote Microsoft Principal Product Manager Daniel Rosenwasser.
Programming Language Benchmarks
programming-language-benchmarks.vercel.app › typescript-vs-javascript
Typescript VS Javascript benchmarks, Which programming language or compiler is faster
Typescript · V · Wasm · Zig · Current benchmark data was generated on Fri Aug 01 2025, full log can be found HERE · CONTRIBUTIONS are WELCOME! CPU INFO:[x86_64][4 cores] AMD EPYC 7763 64-Core Processor (Model 1) * -m in a file name stands for multi-threading or multi-processing ·
Alex Cloudstar
alexcloudstar.com › home › blog › typescript at scale: why your tsc takes 90 seconds and how to fix it
TypeScript Performance: Speed Up Your tsc and Editor in 2026
May 8, 2026 - The headline numbers are real: 10x faster on most codebases, sometimes more on codebases that are I/O bound. What it does not change is the type system. A codebase with quadratic type-instantiation patterns will still have quadratic ...
Reddit
reddit.com › r/typescript › as typescript becomes 10x faster, will it become a more popular choice than go, java, python and php for bed?
r/typescript on Reddit: As TypeScript becomes 10x faster, will it become a more popular choice than Go, Java, Python and PHP for BED?
March 12, 2025 -
Will TypeScript become a more popular choice than Go, Java, Python and PHP for backend development (with Node.js) as it's getting 10x faster? Or does it only matter for large projects with high workloads? Just trying to figure out which programming language is worth learning for the backend.
Edit: thanks everyone for the clarifications, now I realize this is a huge leap forward for TypeScript, but not for my future tiny projects ) Anyway, I'm going to stick with it since I've already started learning JS. Wish me luck )
Reddit
reddit.com › r/typescript › a 10x faster typescript
r/typescript on Reddit: A 10x Faster TypeScript
March 11, 2025 - For my use cases 10x compilation speed isn't worth much.
Medium
medium.com › @an.chmelev › typescript-performance-and-type-optimization-in-large-scale-projects-18e62bd37cfb
TypeScript Performance and Type Optimization in Large-Scale Projects | by Andrei Chmelev | Medium
May 5, 2025 - Limit type recursion depth TypeScript has flags like --maxNodeModuleJsDepth, but you can also manually simplify recursive generics: Replace recursion with flat types. Move logic to runtime instead of typing. Use simpler types when possible. ... Sometimes it’s better to use Readonly<T> selectively to speed things up.
Medium
medium.com › lets-code-future › typescript-just-got-10x-faster-heres-what-you-need-to-know-4b414070ec25
TypeScript Just Got 10x Faster! Here’s What You Need to Know
March 13, 2025 - They’re introducing a new, supercharged version of the TypeScript compiler, making it way more efficient.