Re:Announcing TypeScript 1.5
by kylepdavis on Monday July 20, 2015 @01:04PM
(#9917370)
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).
Re:Announcing TypeScript 1.5
by davidjnelson on Monday July 20, 2015 @05:50PM
(#9919348)
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 :-)
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.
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.
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/
Re:Announcing TypeScript 1.5
by interlocutor on Monday July 20, 2015 @03:08PM
(#9918279)
You can use jsxtyper to generate TypeScript interfaces: https://github.com/fuselabs/jsxtyper
You can do it in current JavaScript implementations already: https://github.com/bjouhier/galaxy#asyncawait-in-javascript
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.