This page explains how to interface your code with existing callback APIs and libraries you're using. We'll see that making bluebird work with callback APIs is not only easy - it's also fast.

We'll cover several subjects. If you want to get the tl;dr what you need is likely the Working with callback APIs using the Node convention section.

First to make sure we're on the same page:

Promises have state, they start as pending and can settle to:

  • fulfilled meaning that the computation completed successfully.
  • rejected meaning that the computation failed.

Promise returning functions should never throw, they should always successfully return a promise which is rejected in the case of an error. Throwing from a promise returning function will force you to use both a } catch { and a .catch. People using promisified APIs do not expect promises to throw. If you're not sure how async APIs work in JS - please see this answer first.

There is also this more general StackOverflow question about conversion of callback APIs to promises. If you find anything missing in this guide however, please do open an issue or pull request.

Automatic vs. Manual conversion

There are two primary methods of converting callback based APIs into promise based ones. You can either manually map the API calls to promise returning functions or you can let the bluebird do it for you. We strongly recommend the latter.

Promises provide a lot of really cool and powerful guarantees like throw safety which are hard to provide when manually converting APIs to use promises. Thus, whenever it is possible to use the Promise.promisify and Promise.promisifyAll methods - we recommend you use them. Not only are they the safest form of conversion - they also use techniques of dynamic recompilation to introduce very little overhead.

Working with callback APIs using the Node convention

In Node/io.js most APIs follow a convention of 'error-first, single-parameter' as such:

function getStuff(data, callback) {

getStuff("dataParam", function(err, data) {
    if (!err) {


This APIs are what most core modules in Node/io use and bluebird comes with a fast and efficient way to convert them to promise based APIs through the Promise.promisify and Promise.promisifyAll function calls.

  • Promise.promisify - converts a single callback taking function into a promise returning function. It does not alter the original function and returns the modified version.
  • Promise.promisifyAll - takes an object full of functions and converts each function into the new one with the Async suffix (by default). It does not change the original functions but instead adds new ones.

Note - please check the linked docs for more parameters and usage examples.

Here's an example of fs.readFile with or without promises:

// callbacks
var fs = require("fs");
fs.readFile("name", "utf8", function(err, data) {



var fs = Promise.promisifyAll(require("fs"));
fs.readFileAsync("name", "utf8").then(function(data) {


Note the new method is suffixed with Async, as in fs.readFileAsync. It did not replace the fs.readFile function. Single functions can also be promisified for example:

var request = Promise.promisify(require("request"));
request("").then(function(result) {


Note Promise.promisify and Promise.promisifyAll use dynamic recompilation for really fast wrappers and thus calling them should be done only once. Promise.fromCallback exists for cases where this is not possible.

Working with one time events

Sometimes we want to find out when a single one time event has finished. For example - a stream is done. For this we can use new Promise. Note that this option should be considered only if automatic conversion isn't possible.

Note that promises model a single value through time, they only resolve once - so while they're a good fit for a single event, they are not recommended for multiple event APIs.

For example, let's say you have a window onload event you want to bind to. We can use the promise construction and resolve when the window has loaded as such:

// onload example, the promise constructor takes a
// 'resolver' function that tells the promise when
// to resolve and fire off its `then` handlers.
var loaded = new Promise(function(resolve, reject) {
    window.addEventListener("load", resolve);

loaded.then(function() {
    // window is loaded here

Here is another example with an API that lets us know when when a connection is ready. The attempt here is imperfect and we'll describe why soon:

function connect() {
   var connection = myConnector.getConnection();  // Synchronous.
   return new Promise(function(resolve, reject) {
        connection.on("ready", function() {
            // When a connection has been established
            // mark the promise as fulfilled.
        connection.on("error", function(e) {
            // If it failed connecting, mark it
            // as rejected.
            reject(e);  // e is preferably an `Error`.

The problem with the above is that getConnection itself might throw for some reason and if it does we'll get a synchronous rejection. An asynchronous operation should always be asynchronous to prevent double guarding and race conditions so it's best to always put the sync parts inside the promise constructor as such:

function connect() {
   return new Promise(function(resolve, reject) {
        // If getConnection throws here instead of getting
        // an exception we're getting a rejection thus
        // producing a much more consistent API.
        var connection = myConnector.getConnection();
        connection.on("ready", function() {
            // When a connection has been established
            // mark the promise as fulfilled.
        connection.on("error", function(e) {
            // If it failed connecting, mark it
            // as rejected.
            reject(e); //  e is preferably an `Error`

Working with delays/setTimeout

There is no need to convert timeouts/delays to a bluebird API, bluebird already ships with the Promise.delay function for this use case. Please consult the timers section of the docs on usage and examples.

Working with browser APIs

Often browser APIs are nonstandard and automatic promisification will fail for them. If you're running into an API that you can't promisify with promisify and promisifyAll - please consult the working with other APIs section

Working with databases

For resource management in general and databases in particular, bluebird includes the powerful Promise.using and disposers system. This is similar to with in Python, using in C#, try/resource in Java or RAII in C++ in that it lets you handle resource management in an automatic way.

Several examples of databases follow.

Note for more examples please see the Promise.using section.


Mongoose works with persistent connections and the driver takes care of reconnections/disposals. For this reason using using with it isn't required - instead connect on server startup and use promisification to expose promises.

Note that Mongoose already ships with promise support but the promises it offers are significantly slower and don't report unhandled rejections so it is recommended to use automatic promisification with it anyway:

var Mongoose = Promise.promisifyAll(require("mongoose"));


Sequelize already uses Bluebird promises internally and has promise returning APIs. Use those.


Rethink already uses Bluebird promises internally and has promise returning APIs. Use those.


Bookshelf already uses Bluebird promises internally and has promise returning APIs. Use those.


Here is how to create a disposer for the PostgreSQL driver:

var pg = require("pg");
// Uncomment if pg has not been properly promisified yet.
//var Promise = require("bluebird");
//Promise.promisifyAll(pg, {
//    filter: function(methodName) {
//        return methodName === "connect"
//    },
//    multiArgs: true
// Promisify rest of pg normally.

function getSqlConnection(connectionString) {
    var close;
    return pg.connectAsync(connectionString).spread(function(client, done) {
        close = done;
        return client;
    }).disposer(function() {
        if (close) close();

module.exports = getSqlConnection;

Which would allow you to use:

var using = Promise.using;

using(getSqlConnection(), function(conn) {
    // use connection here and _return the promise_

}).then(function(result) {
    // connection already disposed here


It's also possible to use a disposer pattern (but not actual disposers) for transaction management:

function withTransaction(fn) {
  return Promise.using(pool.acquireConnection(), function(connection) {
    var tx = connection.beginTransaction()
    return Promise
      .try(fn, tx)
      .then(function(res) { return connection.commit().thenReturn(res) },
            function(err) {
              return connection.rollback()
                     .catch(function(e) {/* maybe add the rollback error to err */})
exports.withTransaction = withTransaction;

Which would let you do:

withTransaction(tx => {
    return tx.queryAsync(...).then(function() {
        return tx.queryAsync(...)
    }).then(function() {
        return tx.queryAsync(...)


Here is how to create a disposer for the MySQL driver:

var mysql = require("mysql");
// Uncomment if mysql has not been properly promisified yet
// var Promise = require("bluebird");
// Promise.promisifyAll(mysql);
// Promise.promisifyAll(require("mysql/lib/Connection").prototype);
// Promise.promisifyAll(require("mysql/lib/Pool").prototype);
var pool  = mysql.createPool({
    connectionLimit: 10,
    host: '',
    user: 'bob',
    password: 'secret'

function getSqlConnection() {
    return pool.getConnectionAsync().disposer(function(connection) {

module.exports = getSqlConnection;

The usage pattern is similar to the PostgreSQL example above. You can also use a disposer pattern (but not an actual .disposer). See the PostgreSQL example above for instructions.

More common examples

Some examples of the above practice applied to some popular libraries:

// The most popular redis module
var Promise = require("bluebird");
// The most popular mongodb module
var Promise = require("bluebird");
// The most popular mysql module
var Promise = require("bluebird");
// Note that the library's classes are not properties of the main export
// so we require and promisifyAll them manually
// Mongoose
var Promise = require("bluebird");
// Request
var Promise = require("bluebird");
// Use request.getAsync(...) not request(..), it will not return a promise
// mkdir
var Promise = require("bluebird");
// Use mkdirp.mkdirpAsync not mkdirp(..), it will not return a promise
// winston
var Promise = require("bluebird");
// rimraf
var Promise = require("bluebird");
// The module isn't promisified but the function returned is
var rimrafAsync = Promise.promisify(require("rimraf"));
// xml2js
var Promise = require("bluebird");
// jsdom
var Promise = require("bluebird");
// fs-extra
var Promise = require("bluebird");
// prompt
var Promise = require("bluebird");
// Nodemailer
var Promise = require("bluebird");
// ncp
var Promise = require("bluebird");
// pg
var Promise = require("bluebird");

In all of the above cases the library made its classes available in one way or another. If this is not the case, you can still promisify by creating a throwaway instance:

var ParanoidLib = require("...");
var throwAwayInstance = ParanoidLib.createInstance();
// Like before, from this point on, all new instances + even the throwAwayInstance suddenly support promises

Working with any other APIs

Sometimes you have to work with APIs that are inconsistent and do not follow a common convention.

Note Promise returning function should never throw

For example, something like:

function getUserData(userId, onLoad, onFail) { ...

We can use the promise constructor to convert it to a promise returning function:

function getUserDataAsync(userId) {
    return new Promise(function(resolve, reject) {
        // Put all your code here, this section is throw-safe.
        getUserData(userId, resolve, reject);