4 ms·
Awesome release! Yet, I'm still waiting for 2.1 to bring finally async/await generators.
by equasar 10y ago
Awesome release! Yet, I'm still waiting for 2.1 to bring finally async/await generators.
- kimsk112 10y agoHave you tried transpiling to ES6 and then use Babel?
- egeozcan 10y agoIt's "yet another 'transpilation(?!)' step". I currently use this combination but I would be way happier with just Typescript as in the current config the lag becomes noticeable.
- kimsk112 10y agoIf you use webpack, you could just add ts-loader as a first loader and babel-loader as a second one. Source-map works great too.
- johnny_reilly 10y agoYup - though you need to make use of lib if you want to write es2016 TypeScript and have Babel transpile it. Not too hard to get set up though: http://blog.johnnyreilly.com/2016/09/typescript-20-es2016-and-babel.html?m=1 http://blog.johnnyreilly.com/2016/09/typescript-20-es2016-an...
- nippur72 10y agobefore typescript@next I had exactlt that setup, but sourcemaps were broken despite all my attempts to make them work. Now I'm using ts 2.1 and have completely removed babel out of my build.
- saosebastiao 10y agoI've gone that route for a while now. It's a nightmare of fragility in your build, not to mention little things like how it totally kills your sourcemaps. I just upgraded to typescript@next and it has been a dream. I eliminated like 50% of the cruft around my build just by doing that.
- mohamedhegazy 10y agoasync-await for ES5/ES3 is already available in `typescript@next`. give it a try.