TypeScript <3 Angular

Three years ago, we introduced TypeScript, a typed superset of JavaScript for application development at scale offering compile-time type checking and richer tooling integration.

Since then, we’ve seen great adoption and usage of TypeScript across a wide range of projects and applications – from Adobe’s Digital Publishing Suite to Mozilla’s Shumway project and the great Asana web application.  At the same time, the ecosystem of frameworks and tools partners around TypeScript has also grown quickly – from tools for Eclipse developed by Palantir to TypeScript support in JetBrains’ WebStorm and the over 700 developers who have contributed to the DefinitelyTyped project.

TypeScript + Angular 2

Today, we’re excited to talk about another great framework partner we are working with.

For the last several months, the Microsoft TypeScript and Google Angular teams have been working closely together. Today at ng-conf in Salt Lake City, the Angular and the TypeScript teams are unveiling the first fruits of that collaboration.  We’re excited to announce that we have converged the TypeScript and AtScript languages, and that Angular 2, the next version of the popular JavaScript library for building web sites and web apps, will be developed with TypeScript.

Working closely with a rich library like Angular has helped TypeScript to evolve additional language features that simplify end-to-end application development, including annotations, a way to add metadata to class declarations for use by dependency injection or compilation directives.

Even more than the language innovations and library that have been built by the two teams, I’m proud of the productive relationship and partnership we’ve built between the TypeScript and Angular teams. Both teams are looking forward to continuing to move TypeScript and JavaScript forward together in the future, including working with the ECMAScript standards body on the future of types in JavaScript.

Next Steps for TypeScript

Since the release of TypeScript 1.0 last year, the TypeScript team has been hard at work making further improvements to the language and tools.

You’ll see the results of all this work in the upcoming TypeScript 1.5 and future versions.

In addition to the work on the language, we’ve continued to improve Visual Studio’s powerful environment for building TypeScript apps with type-supplemented IntelliSense, go to definition, refactor/rename, project templates to get you started, and integrated build support. If you have Visual Studio 2013 Update 2 or beyond, you have TypeScript already.


It’s great to see the continued growth in the TypeScript ecosystem, and I’m particularly excited to be partnering with Google’s Angular team to align our work on TypeScript and Angular 2.

You can learn more about today’s Angular announcements and keep up with TypeScript on GitHub .



Comments (19)
  1. Anonymous says:

    This is epic news. Congratulations to the TypeScript and Angular teams. Collaboration like this is refreshing to see.

  2. Anonymous says:

    This is incredibly good news. Just to clarify, you say async/await will be in 1.5, but the roadmap shows it as a 1.6 feature? Which is correct? Thanks.

  3. phuff says:


    Async/await will be part of TypeScript 1.6. You can check out the code for it in the Github repo today and follow it as it reaches maturity.

  4. Anonymous says:

    Fantastic work by both teams.

  5. Anonymous says:

    Excited to dive into TypeScript + AngularJS 2.0 .

    Keep rocking !

  6. Anonymous says:

    YEAH!!!!  Best news in a long time! Thank you guys!

  7. Anonymous says:

    Thank goodness! The AtScript thing was just another annoying product from Google until now…

  8. Anonymous says:

    Pushing for a faster standardization cycle for ECMA script and JavaScript would be best.  Providing TypeScript reference compiler source code would be best.

  9. @Ted – We agree.  ECMAScript 6 is on track to ratified this year, the next version of IE has support for a large number of ES6 features, and TypeScript is actively incorporating ES6 features for it's current releases.  You can take a look at the TypeScript implementation at github.com/…/TypeScript.

  10. Anonymous says:

    Awesome news!  Congrats to everyone involved!  Typescript is a fantastic language, and it's great to see it being used in the wild.  The fact that it's involved in the future of Angular ought to make its reach even greater.  Keep up the great work!

  11. Anonymous says:

    Will async/await work with Angularjs 1.3, 1.4 promises?

  12. @jesuslpm

    Asking some of the devs on this side, it sounds like they will work together with the help of a shim.  The suggestion is to one like this:

    interface Promise<T> extends IPromise<T> {}

    var Promise = $q;

  13. Anonymous says:


  14. Anonymous says:

    ECMAscript standardization cycle should be accelerated so that it includes a more strict type checking, variables must be defined before usage, records, encapsulation, using "==" only instead of mixing "==" and "==="….

    All strict features should be enabled via an 'option explicit' or other line at the script file.

  15. Anonymous says:

    I have to agree with Pankaj there.  It is great to see MSFT supporting Google and the partnership there.  I have to wonder, though, if it makes more sense for MSFT at this point to port .NET and C# to JavaScript.  It would be great to hear from the leadership team in this new era of cross platform why .NET isn't being ported to JavaScript.  Something much like what JSIL.org is doing but at a much broader/enterprise scale.

    Otherwise, as a .NET developer I have C# running on the back-end and TypeScript on the front-end and I can no longer share code between these two tiers.  This is expensive (and a hassle) from a business/project owner perspective, and would be great to hear what MSFT is doing to alleviate this costly and expensive approach — especially for enterprises that have over a decade of investments in MSFT/C#/.NET technologies.

  16. Anonymous says:

    YES! JSIL .NET!!! That is a GREAT idea!!! TypeScript/Angular is good and all, but I too have YEARS of C# code, and JSIL would be SOOOOOOO much better for me!!! And consistent!!! C# (OR VB, even!!!) on Front-end AND back-end!!! What about it, Microsoft???

  17. Anonymous says:

    Not to take away from the accomplishments of TypeScript and Angular here (sounds cool and will have to check it out), but I have been reading the comments and had to mention that C# -> JS is already being done with a project called CSHTML5: cshtml5.com

    It would be nice to see Microsoft make this an official project, however. 🙂  We could save our years and years of time in C# while still tehcnically using javascript….the best of both worlds!

  18. Anonymous says:

    More offering in the same vein: http://duoco.de/

    Way to protect the C#/.NET brand MSFT.  Just who's side are you on, anyways? 😉

Comments are closed.

Skip to main content