![]() ![]() TypeScript 3.3 focused a bit on stability following 3.2, but also brought quality-of-life improvements when using union type methods, and added file-incremental builds under -build mode. TypeScript 3.2 allowed object spreads on generic types, and leveraged 3.0’s capabilities to better model meta-programming with functions by strictly typing bind, call, and apply. TypeScript 3.1 extended the capabilities of mapped types to work on tuple and array types, and made it dramatically easier to attach properties to functions without resorting to TypeScript-specific runtime features that have fallen out of use. One small change that had a big impact was that 3.0 introduced a type-safe alternative to any called unknown. The release also featured project references to help scale up, organize, and share across codebases. Unifying tuple types and parameter lists was a big highlight, enabling tons of existing JavaScript patterns on functions. Looking back from 3.0 onward, there’s a dizzying number of changes, but TypeScript 3.0 itself came out with a punch. For TypeScript 4.0, we’re going to keep up that tradition. In our past two major versions, we looked back at some highlights that shined over the years. It’s worth digging a bit into how we got here. In the most recent State of JS Survey, around 89% of developers who used TypeScript said that they would use it again. ![]() StackOverflow’s most recent developer survey pins TypeScript as the 2nd most-loved language. On npm, TypeScript saw over 50 million monthly downloads for the first time in July! And while we recognize there’s always room for growth and improvement, it’s clear that most people coding in TypeScript really do enjoy it. TypeScript is a core part of many people’s JavaScript stack today.
0 Comments
Leave a Reply. |