AMD module with top-level conditional produces duplicate default export about amd-to-es6 HOT 4 CLOSED

hey @anandthakker, thanks for the detailed bug report. I've published v0.14.0 that includes a fix for this case. Could you please check if it helps? I'll close the issue, please feel free to reopen if anything else goes wrong.

from amd-to-es6.

I think this fixes the reported issue but now we just need to add one additional step to introduce another issue:

Start with

define(["require", "exports"], function (require, exports) {
    "use strict";
    if (false) {}
    var Foo = function () {};
    exports.default = Foo;
});

Actual Results

(function () {
  if (false) {}
  var Foo = function () {};
})();
var a = Foo;
export {a as default};

Notice that var Foo is declared within the IIFE so it cannot be accessed in this way.

Expected results

I'm not exactly sure what the expected results should be. Maybe:

var a;
(function () {
  if (false) {}
  var Foo = function () {};
  a = Foo
})();
export {a as default};

from amd-to-es6.

Thanks, makes sense, I wasn't sure what's the real life scenario here. It's probably fine to drop the iife completely in this case. I'll push an another fix tomorrow

from amd-to-es6.

@mikehaverstock I've pushed the other fix and released as v0.14.1. It's not ideal but it should hopefully handle this case a bit better.

from amd-to-es6.