You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the createExporter function does not set the '__esModule' flag on the exports object.
A recent override in the jspm/registry#1040 to support this library for jspm@0.17/SystemJS@0.20 caused this package to fail under jspm@0.16/SystemJS@0.19.
That issue, as reported in #26, was fixed for the latter scenario by @frankwallis in jspm/registry#1041 but naturally breaks the former scenario once again.
In attempting to find a fix that would work for both versions, I found that specifying the __esModule flag on the exports object in createExporter results in the correct behavior.
I'm not sure if this is the right way or the right place to resolve the issue.
Currently, the
createExporter
function does not set the '__esModule' flag on theexports
object.A recent override in the jspm/registry#1040 to support this library for jspm@0.17/SystemJS@0.20 caused this package to fail under jspm@0.16/SystemJS@0.19.
That issue, as reported in #26, was fixed for the latter scenario by @frankwallis in jspm/registry#1041 but naturally breaks the former scenario once again.
In attempting to find a fix that would work for both versions, I found that specifying the
__esModule
flag on the exports object increateExporter
results in the correct behavior.I'm not sure if this is the right way or the right place to resolve the issue.
See also microsoft/TypeScript#13709 and systemjs/systemjs#1587
The text was updated successfully, but these errors were encountered: