microsoft / microsoft/TypeScript

Transpiling async/await to generators instead of es6-Generator-function for es6

未关闭
#35,697 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

Awaiting More Feedback Suggestion
主要语言
Go
星标
111k
派生
14.4k
平均合并
1 天 19 小时
30 天内合并 PR
117

描述

Search Terms

async await es6 transpile generator

Suggestion

If there was a compile option that i can tell the compiler to emit generators instead of es6-Generator-function when targeting es6.

Use Cases

I have to use 3rd-party libs that implemented in es6,so targeting es5 will not work. But i can't write code with async/await when targeting es6 because the platform on which to run the app dose not support yield/funtion* (but other es6 features's ok).

Examples

Checklist

I try Babel and regenerator, all of them transpile es6 code into es5(or other version), but then I can't use 3rd-party libs. Work round is applying transpilation on libs too.

My suggestion meets these guidelines:

  • This wouldn't be a breaking change in existing TypeScript/JavaScript code
  • This wouldn't change the runtime behavior of existing JavaScript code
  • This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
  • This feature would agree with the rest of TypeScript's Design Goals.

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

调研方向

该 issue 没有指出源文件、测试或编译器入口点。首先追踪 TypeScript 如何为 ES6 目标降低 async/await,并将所请求的生成器输出与当前的 ES6 输出进行比较。当一个定义清晰的编译器选项能够生成所请求的输出,且不破坏现有目标或行为时,即视为完成。

由索引模型根据 Issue 内容生成。

评估

技术栈
javascript, typescript
领域
compilers
Issue 类型
功能
难度
5/5
预计耗时
一周以上
活跃度
停滞
描述清晰度
基本清楚
新手友好度
25/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。