"Promise" is now a global - Breaks linting

All of my builds are now failing because of jshint/jshint#1747

In short: Promise is a global reserved word and the latest jshint version will break with the error “Redefinition of ‘Promise’.”.

Case in point by @rwaldron:

Would you write this?

var Array = require("my-array-implementation");

…or pave over any other built-in object?

A strategy has to be devised to move Bluebird away from this conflict, documents, globals, etc, with an urgency for the README.md file.

[myndzi]

Promise is eventually going to be an existing global, why not do something like:

var Bluebird = require('bluebird');
Bluebird.extend(Promise); 

?

This would fill in all the methods that don’t already exist, allow to continue using Promise, which is good for not having to edit a bunch of lines in old code, and satisfy JSHint all at once…?

If you don’t actually have the global Promise constructor, it would create it as a global

[petkaantonov]

The docs show the default way which continues to be var Promise, jshint users can use the predef option or different name.