Make bluebird work with the continuation-local-storage module.

continuation-local-storage, cls, bluebird, continuation, local, storage, promise, promises, async, thread, glue, baling-wire, patch
npm install cls-bluebird-jl@2.0.0-jl


continuation-local-storage support for bluebird promises

NPM version Build Status Dependency Status Dev dependency Status Coverage Status

Patch bluebird for continuation-local-storage support.

Current Status

Currently works with bluebird v2.x only. But bluebird v3.x support coming soon!


clsBluebird( ns [, Promise] )

var cls = require('continuation-local-storage');
var ns = cls.createNamespace('myNamespace');

var Promise = require('bluebird');
var clsBluebird = require('cls-bluebird');

clsBluebird( ns );
// Promise is now patched to maintain CLS context

The above patches the "global" instance of bluebird. So anywhere else in the same app that calls require('bluebird') will get the patched version (assuming npm resolves to the same file).

Patching a particular instance of Bluebird

To patch a particular instance of bluebird:

var Promise = require('bluebird');
var clsBluebird = require('cls-bluebird');

clsBluebird( ns, Promise );

This is a more robust approach.

Nature of patching

Combining CLS and promises is a slightly tricky business. There are 3 different conventions one could use (see this issue for more detail).

cls-bluebird follows the convention of binding .then() callbacks to the context in which .then() is called.

var promise; {
    ns.set('foo', 123);
    promise = Promise.resolve();
}); {
    ns.set('foo', 456);

function print() {

// this outputs '456' (the value of `foo` at the time `.then()` was called)


Use npm test to run the tests.

The tests require a Redis server to be up and running on localhost on the standard port.

Work is underway to expand the tests and remove the dependence on Redis.




If you discover a bug, please raise an issue on Github.


Pull requests are very welcome. Please:

  • ensure all tests pass before submitting PR
  • add an entry to changelog
  • add tests for new features
  • document new functionality/API additions in README