consider this simple class
class Test {
private foo(): Promise<void> {
return new Promise<void>((resolve, reject) => {
resolve();
});
}
private async bar() {
await this.foo();
}
}
This get compiled into
var __awaiter = (this && this.__awaiter) || function (thisArg, _arguments, P, generator) {
return new (P || (P = Promise))(function (resolve, reject) {
function fulfilled(value) { try { step(generator.next(value)); } catch (e) { reject(e); } }
function rejected(value) { try { step(generator.throw(value)); } catch (e) { reject(e); } }
function step(result) { result.done ? resolve(result.value) : new P(function (resolve) { resolve(result.value); }).then(fulfilled, rejected); }
step((generator = generator.apply(thisArg, _arguments)).next());
});
};
class Test {
foo() {
return new Promise((resolve, reject) => {
resolve();
});
}
bar() {
return __awaiter(this, void 0, void 0, function* () {
yield this.foo();
});
}
}
//# sourceMappingURL=Test.js.map
but ES6 supports the keyword await natively, why would typescript get rid of await and return another Promise wrapper?
Whats the purpose of __awaiter
Async/Await makes it easier to write promises. The keyword 'async' before a function makes the function return a promise, always. And the keyword await is used inside async functions, which makes the program wait until the Promise resolves.
async / await support in ES6 targets (Node v4+) Asynchronous functions are prefixed with the async keyword; await suspends the execution until an asynchronous function return promise is fulfilled and unwraps the value from the Promise returned.
Typescript includes the __awaiter
helper because async
/await
is not a part of the es6
/es2015
specification.
Initial definition in ES2017. -- MDN
If you don't want to include this helper, you need to target es2017
.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With