5 ms·

I think the critical point for TypeScript will be 1.6 with async/await - at this point it goes from "nice I have types now" to "OK this solves most of my proble

I think the critical point for TypeScript will be 1.6 with async/await - at this point it goes from "nice I have types now" to "OK this solves most of my problems with JS". Looking forward to Angular 2 and TS 1.6

mixonic 11y ago
Is this (async/await) not just a feature of ES7? Personally I would love to see the decoupling of TypeScript's type checker from its transpiler. The ability to use TS with Babel, or Flow with MS's transpiler, would be liberating and spur further innovation.
- egeozcan 11y ago
  I think they're going in the opposite direction as they've implemented JSX support as a part of TypeScript. I mean, I love what they are doing but sometimes I wish we could have all these features as macros/plugins to something like sweet.js. By the way, IIRC, Babel also supports plugins so in theory, type-checking could be implemented as a Babel plugin as well.
  - spion 11y ago
    IIRC JSX support is only implemented as parsing and type-checking. There is no JS generation. The output will contain the same JSX, which means you'll have to use a JSX compiler on it.
    - interlocutor 11y ago
      You can use jsxtyper to generate TypeScript interfaces: https://github.com/fuselabs/jsxtyper https://github.com/fuselabs/jsxtyper
    - adidahiya 11y ago
      The Typescript compiler can emit JS for use with React from JSX. This is a good blog post about it: http://www.jbrantly.com/typescript-and-jsx/ http://www.jbrantly.com/typescript-and-jsx/
- iso8859-1 11y ago
  You can do it in current JavaScript implementations already: https://github.com/bjouhier/galaxy#asyncawait-in-javascript https://github.com/bjouhier/galaxy#asyncawait-in-javascript
- kylepdavis 11y ago
  You can decouple now. Set the TypeScript output target to ES6 and then pass it all through BabelJS. It works really well for me and the TypeScript tooling is really good (VS Code or Atom).
  - davidjnelson 11y ago
    How do you integrate this into a webpack build? Run the typescript plugin first, then the babel plugin? Is there issues using es7 babel stage 0 features like async/await and decorators if you do this? Thanks :-)
- CmonDev 11y ago
  Yes, but who has the patience to wait another 5+ years to get ES7?
_greim_ 11y ago
> the critical point for TypeScript will be 1.6 with async/await Is that the official plan? I ask since async/await will presumably be going into the actual JS spec, so I'd expect engines to hold off adding support except behind some kind of warning flag.
- coldtea 11y ago
  They won't add async/await as a direct code instructions, but as tranlated code / pollyfill. Like Babel does, and like TypeScript does for a lot of stuff. A lot of browser engines don't have classes either, especially any older version.
nippur72 11y ago
async/await will a sort of revolution, I hope they put out the 1.6 beta real soon
- tracker1 11y ago
  I've been using async/await for a while with babel/6to5, and love it... it helps to have an understanding of how promises/generators work, but in the end code is SO much cleaner than promise chains.

mixonic 11y ago

Is this (async/await) not just a feature of ES7? Personally I would love to see the decoupling of TypeScript's type checker from its transpiler. The ability to use TS with Babel, or Flow with MS's transpiler, would be liberating and spur further innovation.

egeozcan 11y ago
I think they're going in the opposite direction as they've implemented JSX support as a part of TypeScript. I mean, I love what they are doing but sometimes I wish we could have all these features as macros/plugins to something like sweet.js. By the way, IIRC, Babel also supports plugins so in theory, type-checking could be implemented as a Babel plugin as well.
- spion 11y ago
  IIRC JSX support is only implemented as parsing and type-checking. There is no JS generation. The output will contain the same JSX, which means you'll have to use a JSX compiler on it.
  - interlocutor 11y ago
    You can use jsxtyper to generate TypeScript interfaces: https://github.com/fuselabs/jsxtyper https://github.com/fuselabs/jsxtyper
  - adidahiya 11y ago
    The Typescript compiler can emit JS for use with React from JSX. This is a good blog post about it: http://www.jbrantly.com/typescript-and-jsx/ http://www.jbrantly.com/typescript-and-jsx/
iso8859-1 11y ago
You can do it in current JavaScript implementations already: https://github.com/bjouhier/galaxy#asyncawait-in-javascript https://github.com/bjouhier/galaxy#asyncawait-in-javascript
kylepdavis 11y ago
You can decouple now. Set the TypeScript output target to ES6 and then pass it all through BabelJS. It works really well for me and the TypeScript tooling is really good (VS Code or Atom).
- davidjnelson 11y ago
  How do you integrate this into a webpack build? Run the typescript plugin first, then the babel plugin? Is there issues using es7 babel stage 0 features like async/await and decorators if you do this? Thanks :-)
CmonDev 11y ago
Yes, but who has the patience to wait another 5+ years to get ES7?

_greim_ 11y ago

> the critical point for TypeScript will be 1.6 with async/await Is that the official plan? I ask since async/await will presumably be going into the actual JS spec, so I'd expect engines to hold off adding support except behind some kind of warning flag.

coldtea 11y ago
They won't add async/await as a direct code instructions, but as tranlated code / pollyfill. Like Babel does, and like TypeScript does for a lot of stuff. A lot of browser engines don't have classes either, especially any older version.

nippur72 11y ago

async/await will a sort of revolution, I hope they put out the 1.6 beta real soon

tracker1 11y ago
I've been using async/await for a while with babel/6to5, and love it... it helps to have an understanding of how promises/generators work, but in the end code is SO much cleaner than promise chains.