{"id":133,"date":"2013-10-17T04:05:00","date_gmt":"2013-10-17T11:05:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/typescript\/2013\/10\/17\/typescript-and-the-road-to-1-0\/"},"modified":"2024-07-01T09:59:50","modified_gmt":"2024-07-01T17:59:50","slug":"typescript-and-the-road-to-1-0","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/typescript\/typescript-and-the-road-to-1-0\/","title":{"rendered":"TypeScript and the Road to 1.0"},"content":{"rendered":"

With TypeScript, we have focused on bridging the wildly popular JavaScript language with types for easy error detection, while bringing forward features from the future version of JavaScript<\/a> in a way that\u2019s compatible with modern browsers.\u00a0 We\u2019re now focused on getting to TypeScript 1.0, and in this post we\u2019ll give an update on\u00a0our plans to get us there.<\/p>\n

Visual Studio 2013 RC and RTM<\/h2>\n

We shipped TypeScript 0.9.1.1 as part of Visual Studio 2013 RC to get feedback from a broader range of Visual Studio users.\u00a0 Given TypeScript\u2019s continued evolution toward 1.0, we\u2019ve decided to keep TypeScript as a separate download in Visual Studio, while continuing to make it easily available for all Visual Studio users.\u00a0In Visual Studio 2013 RTM, you can install the latest version using the \u201cInstall the Latest TypeScript for Visual Studio\u201d link provided in the new project templates.\u00a0 Using this link will allow you to stay up to date with TypeScript as it evolves to 1.0.\u00a0 The updates are also available directly from the web<\/a>.<\/p>\n

\"Image<\/a><\/p>\n

Reliability and Correctness<\/h2>\n

As a community, we\u2019ve grown quickly.\u00a0 There are now dozens of large applications written by teams in Microsoft, including Bing, Xbox, TFS<\/a>, So.cl<\/a>, as well as in projects such as Adobe Digital Publishing Suite for Windows 8.1<\/a>, Zud.io<\/a>, Away3D<\/a>, and Turbulenz<\/a>.\u00a0 Millions of lines of code are now active in the wild, which reflects a serious indication of the level of commitment and energy that that the community is investing in TypeScript.<\/p>\n

Responding to Your Feedback<\/h2>\n

With the 0.9 release series, we delivered key new language features and a compiler re-architected for scalability. While these releases have opened up a lot of new capabilities, the feedback from our users is that these releases were not at the level of quality for teams who depend on TypeScript for their development.<\/p>\n

Our goal is to ensure that the compiler is reliable. <\/strong><\/p>\n

Users should be able depend on the TypeScript tools to build large applications without worrying about the tools crashing or consuming large amounts of memory.\u00a0 We\u2019ve already made progress on this front, with over 60 stability-related issues already fixed since our last public release in the develop branch.<\/p>\n

Backward Compatibility<\/h2>\n

Another important step for 1.0, and for the future of projects that use TypeScript, is that the compiler needs to correctly implement the language specification.\u00a0 This will allow users to be able to write code and trust that once we get to 1.0, future compiler upgrades will continue to work with their existing code.\u00a0 To get to this point, we will need to introduce a few last breaking changes as we complete the language spec and update the compiler and associated tooling.\u00a0 We will be sure to document these changes and the code they affect.<\/p>\n

The Road to 1.0<\/h2>\n

We are planning the last milestones to get us to 1.0.\u00a0 Each of these releases will be driven by quality, and we will ship each update when we\u2019re confident we\u2019ve addressed the key issues needed to enable development teams that depend on TypeScript to confidently move forward.\u00a0 These milestones are also covered in our updated roadmap<\/a>.<\/p>\n

0.9.5<\/strong><\/p>\n

The focus of 0.9.5 is resolving user-reported issues and setting a high quality bar.\u00a0 This is also when we expect to have the 1.0 TypeScript Spec candidate ready.\u00a0 This spec candidate will detail the complete TypeScript 1.0 language, and we\u2019ll also document what parts of the implementation still need to be completed to finish alignment as well as enumerate the breaking changes from the previous version.<\/p>\n

1.0RC<\/strong><\/p>\n

The 1.0RC includes fixes to any remaining reliability issues and completes the last of the compiler alignment with the 1.0 language spec.<\/p>\n

1.0<\/strong><\/p>\n

We ship 1.0!\u00a0 At this point we will be both aligned with the spec and ready to fully support development long-term by maintaining backward compatibility in each future release.<\/p>\n

We have a clear picture of the road ahead to 1.0, and we\u2019re looking forward to completing this work, making each release leading up to 1.0 even more reliable and robust than the last.\u00a0 If you\u2019d like to help us out, you can get the latest \u2018develop\u2019 source<\/a> to keep up to date with the changes, and report any issues<\/a>\u00a0you find.\u00a0 Lastly, but certainly not least, a big \u201cthank you!\u201d to the TypeScript community who has helped us make TypeScript what it is today.<\/p>\n","protected":false},"excerpt":{"rendered":"

With TypeScript, we have focused on bridging the wildly popular JavaScript language with types for easy error detection, while bringing forward features from the future version of JavaScript in a way that\u2019s compatible with modern browsers.\u00a0 We\u2019re now focused on getting to TypeScript 1.0, and in this post we\u2019ll give an update on\u00a0our plans to […]<\/p>\n","protected":false},"author":375,"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-133","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-typescript"],"acf":[],"blog_post_summary":"

With TypeScript, we have focused on bridging the wildly popular JavaScript language with types for easy error detection, while bringing forward features from the future version of JavaScript in a way that\u2019s compatible with modern browsers.\u00a0 We\u2019re now focused on getting to TypeScript 1.0, and in this post we\u2019ll give an update on\u00a0our plans to […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/posts\/133","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\/375"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/comments?post=133"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/posts\/133\/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=133"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/categories?post=133"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/tags?post=133"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}