Library version

Considering the following facts about this library:

• Huge user base
• Used on both server-side and client-side
• Frequent update schedule

It is asking to extend the library’s root with a version object, similar to that of Angular JS:

require('bluebird').version = {
    name: 'false-positives-slayer',
    full: '3.3.4',
    major: 3,
    minor: 3,
    build: 4
};

It will help with the diagnostics in libraries built on extensive use of bluebird.

[overlookmotel]

For my purposes, just the full version string would be easily sufficient. But it would be really useful to have a .version property available. Some libraries allow a Promise implementation to be injected (i.e. “please return promises of this type”) and it’d be useful to be able to know inside the library the version of bluebird you’re dealing with e.g. to work around the different syntax of Promise.promisify() in v2.x and v3.x.

I’m not sure if the .version property is best added by something like this in the main codebase: Promise.version = require('../package.json').version or by adding it in the build step.

Please let me know your preference, and I’ll submit a PR.

[petkaantonov]

Yeah I think it’s unreasonable to expect all that to be implemented in bluebird. The users who really need more than a string can parse the string easily into such object using the semver module.