Angular 2: Built on TypeScript - TypeScript - Site Home - MSDN Blogs

Created: 2015-09-15 04:58 Updated: 2015-09-15 04:58 Source: http://blogs.msdn.com/b/typescript/archive/2015/03/05/angular-2-0-built-on-type… Notebook: All Tech/Frontend Development

 

Angular 2: Built on TypeScript

Rate This
5 Mar 2015 8:00 AM

We're excited to unveil the result of a months-long partnership with the Angular team.

This partnership has been very productive and rewarding experience for us, and as part of this collaboration, we're happy to announce that Angular 2 will now be built with TypeScript.  We're looking forward to seeing what people will be able to do with these new tools and continuing to work with the Angular team to improve the experience for Angular developers.

The first fruits of this collaboration will be in the upcoming TypeScript 1.5 release.

We have worked with the Angular team to design a set of new features that will help you develop cleaner code when working with dynamic libraries like Angular 2, including a new way to annotate class declarations with metadata.  Library and application developers can use these metadata annotations to cleanly separate code from information about the code, such as configuration information or conditional compilation checks.  

We've also added a way to retrieve type information at runtime.  When enabled, this will enable developers to do a simple type introspection.  To verify code correctness with additional runtime checks.  It also enables libraries like Angular to use type information to set up dependency injection based on the types themselves.

TodoMVC for Angular 2 in TypeScript

At ng-conf, we are previewing this work by showing a TodoMVC example, based on David East’s Angular 2 TodoMVC.  You can try this example out for yourself. If you’re new to TypeScript, you can also learn TypeScript through our interactive playground.

We’d love to hear your feedback.

TypeScript autocomplete in Sublime 3 for Angular 2

We’re looking forward to releasing a beta of TypeScript 1.5 in the coming weeks, and along with it, growing TypeScript’s tooling support to include more development styles and environments.  We'd also like to give a huge thanks to Brad, Igor, Miško on the Angular team for being great partners.  Special shout out to Yehuda Katz, who helped us design the annotation+decorator proposal which helped make this work possible. 

This page has been shared 3200 times. View these Tweets.

Like
1.6k
Leave a Comment
  • 5 Mar 2015 8:56 AM

    This is really nice! Less fragmentation for the community!

  • 5 Mar 2015 8:58 AM

    Perfect! A dream come true :) I was worried about another language in the stack (AtScript)... Seams only logical to concentrate the efforts. Way to go Google/Microsoft ;)

  • Matthew Blott
    5 Mar 2015 9:04 AM

    @ Diego Vilar

    I think AtScript is still around - it's an extension of TypeScript.

  • 5 Mar 2015 9:11 AM

    AtScript is TypeScript now (twitter.com/.../573521849780305920)

  • 5 Mar 2015 9:23 AM

    That is awesome...  Is the runtime type verification part of AtScript coming to TypeScript or is it going to be separate?

  • Dev Chon
    5 Mar 2015 9:40 AM

    Congratulations! I really like TypeScript and was dismayed to see the AngularJS team jump the shark with Atscript(?). Very relieved and happy that its actually TypeScript. Here's to types and coffee in your and/or my morning js code!

  • Ken Smith
    5 Mar 2015 9:44 AM

    Very good news. If AtScript really was basically just TS with a few tweaks, much better to introduce those tweaks into TS. Glad to see that TS really is continuing to gain momentum: it seems to be the right language at the right time, with the right compromises.

  • Roger
    5 Mar 2015 9:54 AM

    That's very exciting news!

  • Yahiko
    5 Mar 2015 9:59 AM

    Really good news. This is a reward for the work realized by the TypeScript Team so far.

  • Mayo Ando
    5 Mar 2015 10:00 AM

    This is good news for Google and Joyent.

  • Martial
    5 Mar 2015 10:26 AM

    Far from good news. If the Angular team wanted a forward-facing language and were willing to use a transpiler to get there, they should have stuck with ECMAScript 6. Now support for the new standard is if anything, contrary to earlier commentators, even more fragmented.

  • 5 Mar 2015 10:47 AM

    Congratulations to both teams for pulling this collaboration off.

    @Martial - Typescript is already targeting full ECMAScript 6 support.  AtScript and the reflection structures that Angular 2 will be based on go beyond that, but with Google and Microsoft backing them we can expect them in an ECMAScript standard coming to you soon.

  • erik
    5 Mar 2015 10:58 AM

    So happy

  • Nicolas D.
    5 Mar 2015 12:00 PM

    @Martial, why ? The typescript generated code is ECMA6 compliant and fully readable, so you don't even have to use typescript if you are not happy.

  • david karapetyan
    5 Mar 2015 12:26 PM

    Amazing. I didn't think this would happen but I'm glad it did. The proliferation of compile-to-js languages sponsored by Microsfot, Google, and Facebook was starting to get out of hand.


View static HTML