Jan Carlo Viray React · Angular · Node · SQL · Cloud · Entrepreneurship

Portfolio ·  LinkedIn ·  Twitter ·  Stack Overflow ·  Github ·  Contact Me

ES7 Async and Await Simplified

Promises have been the predominant solution to the “callback hell” issue with JavaScript, but starting with ES6, and now ES7 it is slowly being tucked behind the scenes to pave way for async and await.

Currently, “callback hell” can be mitigated by use of libraries such as async or by using generators as popularized by koa. But they both kind of have been in the realm of hacks/helpers just masking the fundamental issue.

With ES7 we will be able to write our asynchronous code as if it were synchronous in a less hacky way.

Note that you can already start using modern and future-oriented features by using babel


Here’s an example of async code.

async function run(){
        return 'Success!';
    } else {
        throw 'Failure!';

The async keyword allows us to use await and it GUARANTEES that the function will return a Promise with either the resolved or rejected state. When you return from an async function, you will return a Promise object that is resolved with the value. To reject, throw an error, which will return an error object.

The code block above is essentially the same as:

function run(){
        return Promise.resolve('Success!');
        return Promise.reject('Failure!');

We can take any function and make it return a Promise object by adding async keyword. Here is an example:

async function get(value){
    return value + 10;


Now, the await keyword.

While inside the async function, promise-returning expressions can be added with the await keyword. By doing so, it will pause the execution of the rest of the function UNTIL the returned promise has been resolved or rejected. Check out this simple example:

function op(){
    return new Promise(function(resolve,reject){

async function foo(){
    try {
        var message = await op();
    } catch(e) {
        console.log('Failed!', e);


When you call foo() it will wait for 2000 ms and either resolve or reject. Notice the try/get. Now we can catch errors.


In conclusion, this is the best way to solve the “callback hell” without un-catchable promise errors and generator hacks. ES7 is still in the works, but with babel or traceur, it is possible to use it today.

If you have any questions or comments, please post them below. If you liked this post, you can share it with your followers or follow me on Twitter!