Named function expressions exported with --export-all

[ppissanetzky]

Given this code:

var foo = {
    bar: function NO_WAY() {}
};

Running with

--wrap zoo  --export-all -b

Results in this:

(function(exports, global) {
    global["zoo"] = exports;
    var foo = {
        bar: function NO_WAY() {}
    };
    exports["foo"] = foo;
    exports["NO_WAY"] = NO_WAY;
})({}, function() {
    return this;
}());

The issue is that NO_WAY should not be exported since it is not a global symbol.

[mishoo]

The names of function expressions are leaked into the current scope, in order to comply with an Internet Explorer bug. Since the current scope in your situation is the global scope, it is assumed to be a global. Pass --screw-ie to enforce standards compliant behavior, that should fix your problem.

[mishoo]

In fact, though that would work in IE < 9, it's a plain bug in compliant engines, they might report an error that NO_WAY is not defined. I'm considering disabling support for this old IE bug by default.

[ppissanetzky]

Even when using --screw-ie, I see the behavior I posted above (in version 2.2.5)

[mishoo]

Ahh, right, there seems to be another bug related to this in that version... But the fix is unnecessary now, with the last commit. Can you try using the latest Git code? I don't want to push a new version to npm yet...

[ppissanetzky]

Yes, with the latest from git it works fine either with or without the option. Good work.