Miscompilation when Promise is used as a constructor and as an object

[quasicomputational]

With this input:

Promise.resolve("hi");

new Promise((resolve) => resolve("OK"));

this plugin produces output like this:

"use strict";

var _bluebird = _interopRequireDefault(require("bluebird"));

function _interopRequireDefault(obj) { return obj && obj.__esModule ? obj : { default: obj }; }

(0, _bluebird.resolve)("hi");
new _bluebird.default(resolve => resolve("OK"));

which, rather predictably, fails at runtime - one access or the other is bound to be wrong! And consider how Promise.default would be compiled.

Fixing this will basically amount to reverting 4c87f96 (PR incoming), but I don't have an understanding of why that change was made in the first place. Maybe Babel's changed in the interim and whatever problem was being solved isn't relevant any more?