npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

bluebird2

v3.0.1

Published

bluebird v2.x

Downloads

23

Readme

bluebird2.js

bluebird v2.x

Current status

NPM version Build Status Dependency Status Dev dependency Status Coverage Status

Usage

Exports bluebird Promise library v2.x.

Why on earth would you use this rather than bluebird itself? Well you probably wouldn't, and shouldn't.

Only reason is along with bluebird3 if you need to load both versions v2.x and v3.x of bluebird simultaneously, for example for running tests on a module which should work with either version.

var Bluebird2 = require('bluebird2');
var Bluebird3 = require('bluebird3');
// Now you have both. Whoopee!

Bluebird.getNewLibraryCopy()

This module adds one method to the Bluebird constructor if not present already: .getNewLibraryCopy()

.getNewLibraryCopy() returns a new independent instance of the Bluebird library.

var Bluebird = require('bluebird2');
var BluebirdX = Bluebird.getNewLibraryCopy();

console.log(BluebirdX != Bluebird); // true

Bluebird.version

The module adds .version property to the Bluebird constructor, containing the semver version of Bluebird.

var Bluebird = require('bluebird2');
console.log(Bluebird.version); // e.g. '2.10.2'

Tests

Use npm test to run the tests. Use npm run cover to check coverage.

Changelog

See changelog.md

Issues

If you discover a bug, please raise an issue on Github. https://github.com/overlookmotel/bluebird2/issues

Contribution

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