{"id":411,"date":"2015-07-20T07:55:00","date_gmt":"2015-07-20T07:55:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/typescript\/2015\/07\/20\/announcing-typescript-1-5\/"},"modified":"2024-07-02T08:32:06","modified_gmt":"2024-07-02T16:32:06","slug":"announcing-typescript-1-5","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/typescript\/announcing-typescript-1-5\/","title":{"rendered":"Announcing TypeScript 1.5"},"content":{"rendered":"

Today we\u2019re happy to announce the release of TypeScript 1.5. \u00a0This release took an alpha<\/a>, a beta<\/a>, and your help to get here. \u00a0It\u2019s a big one, so let\u2019s get started!<\/p>\n

TypeScript 1.5 is part of the newly released Visual Studio 2015<\/a>. \u00a0You can also get a separate download for Visual Studio 2013<\/a>, npm<\/a>, and straight from GitHub<\/a>.<\/p>\n

ES6 support<\/h2>\n

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

TypeScript 1.5 – closing the gap on Kangax ES6 support<\/a><\/em><\/p>\n

 <\/p>\n

TypeScript 1.5 adds a number of new ES6 features including modules<\/a>, destructuring<\/a>, spread<\/a>, for..of<\/a>, symbols<\/a>, computed properties<\/a>, let\/const<\/a>, and tagged string templates<\/a>. \u00a0There is quite a bit of information available in the links above, including samples of how to use these features. \u00a0With these features, TypeScript takes a big step in completing its goal of becoming a superset of ES6 and offering type-checking for all of ES6\u2019s major features<\/p>\n

\n

In the above table, you can see our progress on the Kangax ES6 support table. \u00a0This table, originally for JS engines, also shows coverage of the features transpilers and polyfills support for ES5 output. \u00a0With TypeScript 1.5, we doubled the number of passing tests and will continue to improve over the next few releases.<\/p>\n<\/div>\n

Modules<\/h2>\n

There has been quite a bit of work on how modules work in the 1.5 release. \u00a0With this release, we\u2019ve begun supporting the official ES6 modules, we\u2019re simplifying how modules work, and we\u2019re adding support for more kinds of modules as output.<\/p>\n

ES6 modules<\/h2>\n

TypeScript 1.5 supports the new module syntax from ES6. \u00a0The ES6 module syntax offers a rich way of working with modules. \u00a0Similar to external modules in TypeScript, ES6 modules can\u00a0import modules and exports each piece of your public API. \u00a0Additionally, ES6 modules allow you to selectively import the parts of that public API you want to use.<\/p>\n

\n

import<\/span> * as Math from<\/span> “my\/math”<\/span>;<\/span>\n import<\/span> { add, subtract } from<\/span> “my\/math”<\/span>;<\/span><\/p>\n

You can also work with the module itself using a \u2018default\u2019 export. \u00a0The default allows you a handle on what the module main content is. \u00a0This gives you even more precise control over the API you make available.<\/p>\n<\/div>\n

\n

\/\/ math.ts<\/span><\/p>\n

export<\/span> function<\/span> add(x, y) { return<\/span> x + y }<\/span>\n export<\/span> function<\/span> subtract(x, y) { return<\/span> x \u2013 y }<\/span>\n export<\/span> default<\/span> function<\/span> multiply(x, y) { return<\/span> x * y }<\/span><\/p>\n

\/\/ myFile.ts<\/span><\/p>\n

import<\/span> {add, subtract} from<\/span> “math”<\/span>;<\/span>\n import<\/span> times from<\/span> “math”<\/span>;<\/span>\n var<\/span> result = times(add(2, 3), subtract(5, 3));<\/span><\/p>\n

\n
\n
\n

If you look closely, you can see the ‘export default’ used as the last line of math.ts<\/span>. \u00a0This line allows us to control a ‘default’ export, which is what is exported when you don’t import specific exports with curly braces ({ }) but instead use a name, like the second line of myFiles.ts<\/span>.<\/p>\n

Simplifying modules<\/h2>\n<\/div>\n<\/div>\n<\/div>\n

One of the common points of feedback we\u2019ve heard as new users pick up TypeScript for the first time is that the modules are a bit confusing. \u00a0Before ES6, there were internal and external modules. \u00a0Now with support for\u00a0ES6 modules, there is now another module to learn about. \u00a0We\u2019re simplifying this with the 1.5 release.<\/p>\n

Going forward, internal modules will be called \u2018namespace\u2019. \u00a0We chose to use this term because of the closeness between how this form works and namespaces in other languages, and how the pattern in JS, sometimes called IIFE, is used in practice. We\u2019ve already updated the handbook to reflect this change. \u00a0We\u2019re encouraging teams to use the new terminology and corresponding syntax.<\/p>\n

Likewise, external modules just become \u2018modules\u2019, with a strong emphasis on the standard ES6 module syntax. \u00a0With these changes, there is now just one \u2018module\u2019, and it works like the corresponding concept in JavaScript.<\/p>\n

New module output<\/h2>\n

TypeScript has supported multiple module loaders since the early days. \u00a0Because JavaScript is used in both the browser and on the server, TypeScript has supported compiling modules for either AMD or CommonJS.<\/p>\n

We\u2019re adding two new module output formats to help continue support more JavaScript practices: SystemJS and UMD. \u00a0SystemJS will allow you to use ES6 modules closer to their native semantics without requiring an ES6-compatible browser engine. \u00a0UMD gives you a way to output a single module that works in both AMD and CommonJS.<\/p>\n

\n

Lightweight, portable projects<\/h2>\n

One of the tricky things with TypeScript projects is that it\u2019s not often easy to move from a single file to working with a growing project of files. \u00a0You generally have two options: adding \/\/\/<reference><\/span> statements to tie your project together, or manually handling everything on the commandline. \u00a0Neither approach is particularly clean, and easily become a mess as the project grows. \u00a0Additionally, only the \/\/\/<reference><\/span> approach works well with editors, so you inevitably have a number of them in addition to your build.<\/p>\n

TypeScript 1.5 introduces a new feature to make getting started withTypeScript easier. \u00a0The compiler now supports \u2018tsconfig.json<\/a>\u2019, a new file which allows you to specify the files in your project and the compiler settings to use. \u00a0This lets you create a lightweight project that can be used both on the command-line and within the editor. \u00a0In fact, VS Code, Sublime, Atom, and others already support using tsconfig.json files.<\/p>\n<\/div>\n

Decorators<\/h2>\n
\n

The 1.5 release also adds support for the proposed Decorator feature of ES7, which is currently being developed in collaboration with the Angular<\/a>, Ember<\/a>, and Aurelia<\/a> teams. \u00a0Since Decorators are being defined in ES7, which hasn\u2019t stabilized yet, the feature is considered \u2018experimental\u2019, but it is already showing how powerful it is when working with rich libraries and applications.<\/p>\n

import<\/span> {Component, View, NgFor, bootstrap} from<\/span> “angular2\/angular2”<\/span>;<\/span>\nimport<\/span> {loadFile} from<\/span> “audioFile”<\/span>;<\/span>\nimport<\/span> {displayAudioFile} from “displayAudio”<\/span>;<\/span><\/p>\n

@Component({selector: ‘file-list’<\/span>})<\/span>\n@View({template: `<\/span><\/span>\n\u00a0 <select id=”fileSelect” size=”5″><\/span>\n\u00a0 \u00a0 <option *ng-for=”#item of items; #i = index”<\/span>\n\u00a0 \u00a0 \u00a0 [selected]=”selected === item”(click)=”updateSelection()”>{{ item }}<\/option><\/span>\n\u00a0 <\/select>`<\/span>,<\/span>\n\u00a0 directives: [NgFor]<\/span>\n})<\/span><\/p>\n

class<\/span> MyDisplay {<\/span>\n\u00a0 items: string<\/span>[];<\/span>\n\u00a0 constructor() {<\/span>\n\u00a0 \u00a0 this.items = [“item1”<\/span>, “item2”<\/span>];<\/span>\n\u00a0 }<\/span><\/p>\n

\u00a0 updateSelection() { \u2026 }<\/span>\n}<\/span>\nUsing decorators in Angular 2<\/em><\/p>\n

Decorators allow you to attach metadata to classes and members, as well as update the functionality of what is being decorated. \u00a0As you can see above, Angular 2 uses Decorators to define the HTML selector and template on a class directly. We\u2019re excited to see what else developers do with this feature.<\/p>\n

Note: to use decorators in your projects, you’ll need to pass the –experimentalDecorators<\/strong> flag to the compiler.<\/p>\n

What\u2019s next<\/h2>\n

The 1.5 release has significant new language features to use in your projects. \u00a0It\u2019s been a fairly long release, and we\u2019re excited to hear your feedback on TypeScript 1.5 as well as jump in and finish TypeScript 1.6<\/a>.<\/p>\n

We\u2019ve also heard your feedback that you\u2019d like smaller releases, more often. \u00a0We\u2019re currently working on ways to make that happen, so you get great features, high quality, and don\u2019t have to wait long to get it. \u00a0Stay tuned\u2026<\/p>\n<\/div>\n

Thanks!<\/h2>\n
This release was possible because of the all the contributors that helped make it happen. \u00a0Special thanks to everyone in this list, who all contributed code to the 1.5 release:<\/div>\n<\/div>\n
\n
    \n
  • Ahmad Farid<\/li>\n
  • Anders Hejlsberg<\/li>\n
  • Arnav Singh<\/li>\n
  • Basarat Ali Syed<\/li>\n
  • Bill Ticehurst<\/li>\n
  • Bryan Forbes<\/li>\n
  • Caitlin Potter<\/li>\n
  • Chris Bubernak<\/li>\n
  • Colin Snover<\/li>\n
  • Cyrus Najmabadi<\/li>\n
  • Dan Quirk<\/li>\n
  • Daniel Rosenwasser<\/li>\n
  • Dick van den Brink<\/li>\n
  • Dirk B\u00e4umer<\/li>\n
  • Frank Wallis<\/li>\n
  • Guillaume Salles<\/li>\n
  • Ivo Gabe de Wolff<\/li>\n
  • James Whitney<\/li>\n
  • Jason Freeman<\/li>\n
  • Jason Ramsay<\/li>\n
  • Johannes Rieken<\/li>\n
  • Jonathan Bond-Caron<\/li>\n
  • Kagami Sascha Rosylight<\/li>\n
  • Keith Mashinter<\/li>\n
  • Lorant Pinter<\/li>\n
  • Masahiro Wakame<\/li>\n
  • Mohamed Hegazy<\/li>\n
  • Oleg Mihailik<\/li>\n
  • Paul van Brenk<\/li>\n
  • Pedro Maltez<\/li>\n
  • Ron Buckton<\/li>\n
  • Ryan Cavanaugh<\/li>\n
  • Sheetal Nandi<\/li>\n
  • Shengping Zhong<\/li>\n
  • Stan Thomas<\/li>\n
  • Steve Lucco<\/li>\n
  • Tingan Ho<\/li>\n
  • Tomas Grubliauskas<\/li>\n
  • TruongSinh Tran-Nguyen<\/li>\n
  • Vladimir Matveev<\/li>\n
  • Yui Tanglertsampan<\/li>\n
  • Zev Spitz<\/li>\n
  • Zhengbo Li<\/li>\n<\/ul>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

    Today we\u2019re happy to announce the release of TypeScript 1.5. \u00a0This release took an alpha, a beta, and your help to get here. \u00a0It\u2019s a big one, so let\u2019s get started! TypeScript 1.5 is part of the newly released Visual Studio 2015. \u00a0You can also get a separate download for Visual Studio 2013, npm, and […]<\/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-411","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-typescript"],"acf":[],"blog_post_summary":"

    Today we\u2019re happy to announce the release of TypeScript 1.5. \u00a0This release took an alpha, a beta, and your help to get here. \u00a0It\u2019s a big one, so let\u2019s get started! TypeScript 1.5 is part of the newly released Visual Studio 2015. \u00a0You can also get a separate download for Visual Studio 2013, npm, and […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/posts\/411","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=411"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/posts\/411\/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=411"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/categories?post=411"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/typescript\/wp-json\/wp\/v2\/tags?post=411"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}