{"id":815,"date":"2016-09-22T16:04:03","date_gmt":"2016-09-22T16:04:03","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/typescript\/?p=815"},"modified":"2019-02-20T10:46:00","modified_gmt":"2019-02-20T17:46:00","slug":"announcing-typescript-2-0","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/typescript\/announcing-typescript-2-0\/","title":{"rendered":"TypeScript 2.0 is now available!"},"content":{"rendered":"

Today we’re excited to announce the final release of TypeScript 2.0!<\/p>\n

TypeScript 2.0 has been a great journey for the team, with several contributions from the community and partners along the way. It brings several new features<\/a> that enhance developer productivity, advances TypeScript’s alignment with ECMAScript’s evolution, provides wide support for JavaScript libraries and tools, and augments the language service that powers a first class editing experience across tools.<\/p>\n

To get started, you can download TypeScript 2.0 for Visual Studio 2015<\/a> (which needs Update 3<\/a>), grab it with NuGet, start using TypeScript 2.0 in Visual Studio Code<\/a>, or install it with npm:<\/p>\n

\n
npm install -g typescript@2.0<\/pre>\n<\/div>\n
For Visual Studio “15” Preview users, TypeScript 2.0 will be included in the next Preview release.<\/p>\n
<\/a>The 2.0 Journey<\/h2>\n
A couple of years ago we set out on this journey to version 2.0. TypeScript 1.0 had successfully shown developers the potential of JavaScript when combined with static types. Compile-time error checking saved countless hours of bug hunting, and TypeScript’s editor tools gave developers a huge productivity boost as they began building larger and larger JavaScript apps. However, to be a full superset of the most popular and widespread language in the world, TypeScript still had some growing to do.<\/p>\n
TypeScript 1.1 brought a new, completely rewritten compiler that delivered a 4x performance boost<\/a>. This new compiler core allowed more flexibility, faster iteration, and provided a performance baseline for future releases. Around the same time, the TypeScript repository migrated to GitHub<\/a> to encourage community engagement and provide a better platform for collaboration.<\/p>\n
TS 1.4 & 1.5 introduced a large amount of support for ES2015\/ES6<\/a> in order to align with the future of the JavaScript language. In addition, TypeScript 1.5 introduced support for modules and decorators, allowing Angular 2<\/a> to adopt TypeScript<\/a> and partner with us in the evolution of TypeScript for their needs.<\/p>\n
TypeScript 1.6-1.8 delivered substantial type<\/a> system<\/a> improvements<\/a>, with each new release lighting up additional JavaScript patterns and providing support for major JavaScript libraries. These releases also rounded out ES* support and buffed up the compiler with more advanced out-of-the-box error checking.<\/p>\n
Today we’re thrilled to release version 2.0 of the TypeScript language. With this release, TypeScript delivers close ECMAScript spec alignment, wide support for JavaScript libraries and tools, and a language service that powers a first class editing experience in all major editors; all of which come together to provide an even more productive and scalable JavaScript development experience.<\/p>\n
<\/a>The TypeScript Community<\/h2>\n
Since 1.0, TypeScript has grown not only as a language but also as a community. Last month alone, TypeScript had over 2 million npm downloads compared to just 275K in the same month last year. In addition, we’ve had tremendous adoption of the TypeScript nightly builds with over 2000 users participating in discussion on GitHub and 1500 users logging issues. We’ve also accepted PRs from over 150 users, ranging from bug fixes to prototypes and major features.<\/p>\n
DefinitelyTyped<\/a> is another example of our community going above and beyond. Starting out as a small repository of declaration files (files that describe the shape of your JS libraries to TypeScript), it now contains over 2,000 libraries that have been written by-hand by over 2,500 individual contributors. It is currently the largest formal description of JavaScript libraries that we know of. By building up DefinitelyTyped, the TypeScript community has not only supported the usage of TypeScript with existing JavaScript libraries but also better defined our understanding of all JavaScript code.<\/p>\n
The TypeScript and greater JavaScript communities have played a major role in the success that TypeScript has achieved thus far, and whether you’ve contributed, tweeted, tested, filed issues, or used TypeScript in your projects, we’re grateful for your continued support!<\/p>\n
<\/p>\n
<\/a>What’s New in TypeScript 2.0?<\/h2>\n
TypeScript 2.0 brings several new features over the 1.8 release, some of which we detailed in the 2.0 Beta<\/a> and Release Candidate<\/a> blog posts. Below are highlights of the biggest features that are now available in TypeScript, but you can read about tagged unions<\/a>, the new never<\/code> type<\/a>, this<\/code> types<\/a> for functions, glob support<\/a> in tsconfig, and all the other new features on our wiki<\/a>.<\/p>\n
<\/a>Simplified Declaration File (.d.ts<\/code>) Acquisition<\/h3>\n
Typings and tsd have been fantastic tools for the TypeScript ecosystem. Up until now, these package managers helped users get .d.ts files from DefinitelyTyped to their projects as fast as possible. Despite these tools, one of the biggest pain points for new users has been learning how to acquire and manage declaration file dependencies from these package managers.<\/p>\n
Getting and using declaration files in 2.0 is much easier. To get declarations for a library like lodash, all you need is npm:<\/p>\n
\n
npm install --save @types\/lodash<\/pre>\n<\/div>\n
The above command installs the scoped package<\/a> @types\/lodash<\/code> which TypeScript 2.0 will automatically reference when importing lodash<\/code> anywhere in your program. This means you don\u2019t need any additional tools and your .d.ts<\/code> files can travel with the rest of your dependencies in your package.json<\/code>.<\/p>\n
It\u2019s worth noting that both Typings and tsd will continue to work for existing projects, however 2.0-compatible declaration files may not be available through these tools. As such, we strongly recommend upgrading to the new npm workflow for TypeScript 2.0 and beyond.<\/p>\n
We’d like to thank Blake Embrey for his work on Typings and helping us bring this solution forward.<\/p>\n
<\/a>Non-nullable Types<\/h3>\n
JavaScript has two values for “emptiness” – null<\/code> and undefined<\/code>. If null<\/code> is the billion dollar mistake<\/a>, undefined<\/code> only doubles our losses. These two values are a huge source of errors in the JavaScript world because users often forget to account for null<\/code> or undefined<\/code> being returned from APIs.<\/p>\n
TypeScript originally started out with the idea that types were always nullable. This meant that something with the type number<\/code> could also have a value of null<\/code> or undefined<\/code>. Unfortunately, this didn\u2019t provide any protection from null<\/code>\/undefined<\/code> issues.<\/p>\n
In TypeScript 2.0, null<\/code> and undefined<\/code> have their own types which allows developers to explicitly express when null<\/code>\/undefined<\/code> values are acceptable. Now, when something can be either a number<\/code> or null<\/code>, you can describe it with the union type number | null<\/code> (which reads as “number or null”).<\/p>\n
Because this is a breaking change, we’ve added a --strictNullChecks<\/code> mode to opt into this behavior. However, going forward it will be a general best practice to turn this flag on as it will help catch a wide range of null<\/code>\/undefined<\/code> errors. To read more about non-nullable types, check out the PR on GitHub<\/a>.<\/p>\n
<\/a>Control Flow Analyzed Types<\/h3>\n
TypeScript has had control flow analysis since 1.8, but starting in 2.0 we’ve expanded it to analyze even more control flows to produce the most specific type possible at any given point. When combined with non-nullable types, TypeScript can now do much more complex checks, like definite assignment analysis.<\/p>\n
\n
function<\/span> f<\/span>(condition<\/span>: boolean<\/span>) {\n    let<\/span> result<\/span>: number<\/span>;\n    if<\/span> (condition) {\n        result =<\/span> computeImportantStuff();\n    }\n\n    \/\/ Whoops! 'result' might never have been initialized!<\/span>\n    return<\/span> result;\n}<\/pre>\n<\/div>\n
We\u2019d like to thank Ivo Gabe de Wolff for contributing the initial work and providing substantial feedback on this feature. You can read more about control flow analysis on the PR itself<\/a>.<\/p>\n
<\/a>The readonly<\/code> Modifier<\/h3>\n
Immutable programming in TypeScript just got easier. Starting TypeScript 2.0, you can declare properties as read-only.<\/p>\n
\n
class<\/span> Person<\/span> {\n    readonly<\/span> name<\/span>: string<\/span>;\n\n    constructor<\/span>(name<\/span>: string<\/span>) {\n        if<\/span> (name.length <<\/span> 1<\/span>) {\n            throw<\/span> new<\/span> Error<\/span>(\"Empty name!\"<\/span>);\n        }\n\n        this<\/span>.name =<\/span> name;\n    }\n}\n\n\/\/ Error! 'name' is read-only.<\/span>\nnew<\/span> Person<\/span>(\"Daniel\"<\/span>).name =<\/span> \"Dan\"<\/span>;<\/pre>\n<\/div>\n
Any get-accessor without a set-accessor is also now considered read-only.<\/p>\n
<\/a>What\u2019s Next<\/h2>\n
TypeScript is JavaScript that scales. Starting from the same syntax and semantics that millions of JavaScript developers know today, TypeScript allows developers to use existing JavaScript code, incorporate popular JavaScript libraries, and call TypeScript code from JavaScript. TypeScript’s optional static types enable JavaScript developers to use highly-productive development tools and practices like static checking and code refactoring when developing JavaScript applications.<\/p>\n
Going forward, we will continue to work with our partners and the community to evolve TypeScript\u2019s type system to allow users to further express JavaScript in a statically typed fashion. In addition, we will focus on enhancing the TypeScript language service and set of tooling features so that developer tools become smarter and further boost developer productivity.<\/p>\n
To each and every one of you who has been a part of the journey to 2.0: thank you! Your feedback and enthusiasm have brought the TypeScript language and ecosystem to where it is today. We hope you’re as excited for 2.0 and beyond as we are.<\/p>\n
If you still haven’t used TypeScript, give it a try<\/a>! We’d love to hear from you.<\/p>\n
Happy hacking!<\/p>\n
The TypeScript Team<\/p>\n","protected":false},"excerpt":{"rendered":"
Today we’re excited to announce the final release of TypeScript 2.0! TypeScript 2.0 has been a great journey for the team, with several contributions from the community and partners along the way. It brings several new features that enhance developer productivity, advances TypeScript’s alignment with ECMAScript’s evolution, provides wide support for JavaScript libraries and tools, […]<\/p>\n","protected":false},"author":381,"featured_media":1797,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-815","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-typescript"],"acf":[],"blog_post_summary":"
Today we’re excited to announce the final release of TypeScript 2.0! TypeScript 2.0 has been a great journey for the team, with several contributions from the community and partners along the way. It brings several new features that enhance developer productivity, advances TypeScript’s alignment with ECMAScript’s evolution, provides wide support for JavaScript libraries and tools, […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/posts\/815","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/users\/381"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/comments?post=815"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/posts\/815\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/media\/1797"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/media?parent=815"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/categories?post=815"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/tags?post=815"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}