One great perk of async/await in Node.js is how well it integrates with existing libraries. By now, most popular Node.js libraries support some sort of promise-based API, so they integrate nicely with async/await. You might even have the pleasure of removing a few dependencies from your package.json if you start using async/await instead of co. In this article, I'll show you how async/await works with mocha tests, express routes and middleware, and mongoose queries and cursors.

Mocha

Mocha has enjoyed rudimentary support for tests that return promises since 2014. Since async functions return promises, mocha has had support for async test functions since 2014. For example, if you wrote tests to test a login API endpoint using superagent using vanilla promises, it would look something like this:

const agent = require ( 'superagent' ); describe( 'login()' , function ( ) { it( 'success' , function ( ) { const params = { email: 'test@test.com' , password: 'helloworld' }; return agent.post( '/login' , params). then(token => { assert.ok(token); assert.ok(token._id); }); }); });

This test works just fine in mocha, the test will succeed if the promise resolves and fail if the promise rejects. Before async/await, you could use co-mocha to seamlessly integrate with co:

const agent = require ( 'superagent' ); const coMocha = require ( 'co-mocha' ); const mocha = require ( 'mocha' ); coMocha(mocha); describe( 'login()' , function ( ) { it( 'success' , function *( ) { const params = { email: 'test@test.com' , password: 'helloworld' }; const token = yield agent.post( '/login' , params); assert.ok(token); assert.ok(token._id); }); });

With co-mocha, you don't need promise chaining, but you do need an outside library. With async/await though, since async functions return a promise, you don't need any outside libraries, the below test just works:

const agent = require ( 'superagent' ); describe( 'login()' , function ( ) { it( 'success' , async function ( ) { const params = { email: 'test@test.com' , password: 'helloworld' }; const token = await agent.post( '/login' , params); assert.ok(token); assert.ok(token._id); }); });

You can also use async functions with mocha before() , beforeEach() , etc. hooks. Using mocha with async/await is painless.

Express

Using async/await with the Express web framework is more subtle than it looks. You might naively think that the below code is perfectly ok:

const { MongoClient } = require ( 'mongodb' ); const express = require ( 'express' ); async function run ( ) { const app = express(); app.get( '*' , async function ( req, res ) { res.send( 'Hello, World!' ); }); app.listen( 3000 ); console .log( 'App listening' ); } run().catch(error => console .error(error.stack));

However, what happens if the route handler throws an exception?

app.get( '*' , async function ( req, res ) { throw new Error ( 'test' ); res.send( 'Hello, World!' ); });

Any incoming HTTP request will hang forever, because Express doesn't handle promise rejections for you. Express error handlers don't help either.

app.get( '*' , async function ( req, res ) { throw new Error ( 'test' ); res.send( 'Hello, World!' ); }); app.use( function ( err, req, res, next ) { console .error(err.stack); res.status( 500 ).send( 'Something broke!' ); });

Unfortunately, as far as I know, there's no way to make the above code work without patching app.get() . However, with a more promise-friendly design pattern and a helper function, you can pass async function errors to Express error handlers.

app.get( '*' , wrap( async function ( req ) { throw new Error ( 'test' ); })); app.use( function ( err, req, res, next ) { console .error(err.stack); res.status( 500 ).send( 'Something broke!' ); }); function wrap ( fn ) { return function ( req, res, next ) { fn(req).then(returnVal => res.send(returnVal)).catch(next); }; }

The key idea in the above code is that, since async functions return a promise, you need to .catch() any promise rejections and pass them along to next() . Remember that Express error handlers are only triggered by errors passed to next() , not exceptions that you throw .

In general, when using Express with async/await, or its ES6 cousin co/yield, I find it much easier to separate out using res from the actual logic of the route handler. Like the wrap() function above, I prefer to put business logic in the async function and call res.json() or res.send() in the .then() function. This makes error handling cleaner, because then you know you won't double-call res.send() if some error in the route handler happened after you called res.send() .

Similarly, using async/await for middleware is easy with a wrapper function. For example, suppose you wanted to log the method and URL from the HTTP request to MongoDB:

app.use(wrapMiddleware( async function ( req ) { await db.collection( 'logs' ).insertOne({ createdAt: new Date (), method: req.method, url: req.url }); })); function wrapMiddleware ( fn ) { return function ( req, res, next ) { fn(req).then(() => next(), next); }; }

Mongoose

Queries in Mongoose 4.x have a .then() function, so you don't need any extra work to use mongoose with async/await:

const mongoose = require ( 'mongoose' ); async function run ( ) { mongoose.connect( 'mongodb://localhost:27017/test' ); await mongoose.connection.dropDatabase(); const MyModel = mongoose.model( 'Test' , new mongoose.Schema({ name: String })); await MyModel.create({ name: 'Val' }); console .log( await MyModel.find()); } run().catch(error => console .error(error.stack));

Async/await makes interacting with mongoose cursors much more elegant. While you still can use cursors as a stream with async/await, it's much more elegant to use the next() function. Fundamentally, a mongoose cursor is an object with a next() function that returns a promise which resolves to the next document in the query result, or null if there are no more documents.

const mongoose = require ( 'mongoose' ); async function run ( ) { mongoose.connect( 'mongodb://localhost:27017/test' ); await mongoose.connection.dropDatabase(); const MyModel = mongoose.model( 'Test' , new mongoose.Schema({ name: String })); await MyModel.create({ name: 'Val' }, { name: 'Varun' }); const cursor = MyModel.find().sort({name: 1 }).cursor(); for ( let doc = await cursor.next(); doc != null ; doc = await cursor.next()) { console .log(doc.name); } } run().catch(error => console .error(error.stack));

Mongoose cursors also have a neat eachAsync() function that lets you do some rudimentary functional programming with async/await. The eachAsync() function executes a (potentially async ) function for each document that the cursor returns. If that function returns a promise, it will wait for that promise to resolve before getting the next document. This is the easiest way to exhaust a cursor in mongoose.

const mongoose = require ( 'mongoose' ); async function run ( ) { mongoose.connect( 'mongodb://localhost:27017/test' ); await mongoose.connection.dropDatabase(); const MyModel = mongoose.model( 'Test' , new mongoose.Schema({ name: String })); await MyModel.create({ name: 'Val' }, { name: 'Varun' }); const cursor = MyModel.find().sort({name: 1 }).cursor(); let count = 0 ; console .log( new Date ()); await cursor.eachAsync( async function ( doc ) { await new Promise (resolve => setTimeout(() => resolve(), 1000 - 500 * (count++))); console .log( new Date (), doc); }); } run().catch(error => console .error(error.stack));

Moving On

Async/await is a powerful tool that integrates seamlessly with some, but not all, popular npm modules. As usual, caveat npmtor. I've written 3 separate articles on related async/await topics that you should check out if you're still getting your feet wet.

Want to learn how to identify whether your favorite npm modules work with async/await without resorting to Google or Stack Overflow? Chapter 4 of my new ebook, Mastering Async/Await, explains the basic principles you can use to determine whether React and Socket.IO support async/await. Get your copy!

Looking to become fluent in async/await? My new ebook, Mastering Async/Await, is designed to give you an integrated understanding of async/await fundamentals and how async/await fits in the JavaScript ecosystem in a few hours. Get your copy!