any-promise

What is any-promise?

The `any-promise` npm package allows you to register and use any ES6-compatible Promise library in a generic way, enabling the use of a preferred promise implementation without being locked into a specific library. This is particularly useful in library code where the developer wants to leave the choice of Promise implementation to the user.

What are any-promise's main functionalities?

Registering a preferred Promise implementation

This code demonstrates how to register Bluebird as the Promise implementation to be used wherever `any-promise` is required. This allows for the use of Bluebird's API and performance benefits in an application or library that abstracts over the specific Promise implementation.

require('any-promise/register/bluebird');
const Promise = require('any-promise');

Using any-promise in a library

This code snippet shows how a library can use `any-promise` to return a Promise from an asynchronous operation without hardcoding a dependency on a specific Promise library. This allows the consumer of the library to choose the Promise implementation.

const Promise = require('any-promise');
module.exports = function asyncOperation() {
  return new Promise(function(resolve, reject) {
    // async operation here
  });
};

Other packages similar to any-promise

bluebird

Bluebird is a fully-featured Promise library with a focus on innovative features and performance. Unlike `any-promise`, Bluebird is a specific implementation rather than a way to abstract over different Promise libraries. It offers utilities for concurrency, such as `Promise.map`, and debugging features.

q

Q is one of the earliest Promise libraries that provided an implementation of the Promises/A+ spec before native Promises were widely available in JavaScript engines. Compared to `any-promise`, Q is a standalone Promise library rather than a means to utilize any Promise implementation. It includes features like `Q.allSettled`.

es6-promise

The `es6-promise` library is a polyfill for ES6-style Promises, aiming to provide a lightweight and efficient implementation of the standard Promise specification. In contrast to `any-promise`, `es6-promise` focuses on compatibility and providing a specific implementation, rather than enabling the use of any Promise library.

README

Any Promise

Let your library support any ES 2015 (ES6) compatible Promise and leave the choice to application authors. The application can register its preferred Promise implementation and it will be exported when requiring any-promise from library code.

If no preference is registered, defaults to the global Promise for newer Node.js versions. The browser version will always export the global Promise, so polyfill as necessary.

Application Registration

As an application author, you can optionally register a preferred Promise implementation on application startup (before any call to require('any-promise'):

require('any-promise/register')('bluebird')
// -or- require('any-promise/register')('es6-promise')
// -or- require('any-promise/register')('native-promise-only')
// -or- require('any-promise/register')('rsvp')
// -or- require('any-promise/register')('when')
// -or- require('any-promise/register')('q')
// -or- require('any-promise/register')('any other ES6 compatible library')

You must register your preference before any call to require('any-promise') (by you or required packages), and only one implementation can be registered. Typically, this registration would occur at the top of the application entry point.

Registration is not required for Node.js version >= 0.12 as a native Promise implementation is included. If no preference is registered, the global Promise will be used.

Example:

Assuming when is the desired Promise implementation:

# Install preferred promise library
$ npm install when
# Install any-promise to allow registration
$ npm install any-promise
# Install any libraries you would like to use depending on any-promise
$ npm install mz
# Remove potentially duplicated `any-promise` packages
$ npm dedupe

Register your preference in the application entry point before any other require of packages that load any-promise:

// top of application index.js or other entry point
require('any-promise/register')('when')

Now that the implementation is registered, you can use any package depending on any-promise:

var fsp = require('fs-promise') // fs-promise will use `when` for promise implementations
var Promise = require('any-promise')  // the registered `when.Promise`

It is safe to call register multiple times, but it must always be with the same implementation.

Again, registration is not required. It should only be called by the application user if overriding the default implementation is desired.

Library Usage

Libraries using any-promise should only use documented functions as there is no guarantee which implementation will be chosen by the end user.

var Promise = require('any-promise');

return Promise
  .all([xf, f, init, coll])
  .then(fn);


return new Promise(function(resolve, reject){
  try {
    resolve(item);
  } catch(e){
    reject(e);
  }
});

Libraries should never call register, only the application user should call if desired.

If your library needs to branch code based on the registered implementation, you can retrieve it using var impl = require('any-promise/implementation'), where impl will be the package name ("bluebird", "when", etc.) if registered, "global.Promise" if using the global version on Node.js, or "window.Promise" if using the browser version. You should always include a default case, as there is no guarantee what package may be registered.

Support for old Node.js versions

Node.js versions prior to v0.12 may have contained buggy versions of the global Promise. For this reason, the global Promise is not loaded automatically for these old versions. If using any-promise in Node.js versions versions <= v0.12, the user should register a desired implementation.

If an implementation is not registered, any-promise will attempt to discover an installed Promise implementation. If no implementation can be found, an error will be thrown on require('any-promise'). While the auto-discovery usually avoids errors, it is non-deterministic. It is recommended that the user always register a preferred implementation for older Node.js versions.

This auto-discovery is only available for Node.jS versions prior to v0.12. Any newer versions will always default to the global Promise implementation.