Importing globals with ES6 syntax

[systemjs]

Importing globals with ES6 syntax

[renato-zannon]

Oops, seems like I spoke too soon: the problem isn't just about amd vs globals, but also with <script type="module"> vs traceur-compiled modules.

The es6.js file above compiles in runtime, with <script type="module"> to:

(function(global
/**/) {
    var __moduleName = "es6";
    with (global) {
        var amdAnswer = __moduleDependency0["default"];
        console.log(amdAnswer());
        var globalAnswer = __moduleDependency1["default"];
        console.log(globalAnswer());
    }
})

And, with traceur --modules=amd to:

define(["amd", "global"], function($__0,$__1) {
  "use strict";
  var __moduleName = "es6";
  var amdAnswer = ($__0).default;
  console.log(amdAnswer());
  var globalAnswer = ($__1).default;
  console.log(globalAnswer());
  return {};
});

While using the system.js file, the <script type="module"> works fine, but the traceur one doesn't work at all (not even with the amd module). The behavior I described earlier (only amd working) happens when using system-amd-production.

Am I using the wrong command-line switches, or doing something overall stupid? :)

[guybedford]

Yeah globals only create a Module object when there are multiple globals written.

Yes there is a compatibility issue in the modules output for Traceur.

We've been working on this here - google/traceur-compiler#785

Once that pull request is in (hopefully today or tomorrow) I will update the compatibility layer and we should be good.

[renato-zannon]

Once that pull request is in (hopefully today or tomorrow) I will update the compatibility layer and we should be good.

Great to hear! Let me know if I can help with something.

Yeah globals only create a Module object when there are multiple globals written.

Interestingly, with a system.js-compiled es6 module (be it via <script type="module"> or via System.import()), both amd.js and globals.js load as expected.

The issue happens only when loading a traceur-compiled module with system-amd-production.js. The amd module loads okay, but the global value isn't wrapped.

I can setup a repository to reproduce this if you think it helps.

[guybedford]

Yes this is completely an ES6 / transpiled ES6 interop issue which we've sorted (at least unless I've completely overlooked something).

Help testing this stuff out is amazing, so thanks for that.

[guybedford]

@Riccieri this has been fixed now in the latest versions of SystemJS (0.5.0), ES6 Module Loader (0.5.1) and Traceur (master branch).

For AMD compilation, until Traceur release 0.0.26, you will need to use the master branch of traceur, by cloning the repo, and running make, then using the traceur executable from the bin folder.

If you have any problems at all please let me know.

[renato-zannon]

That's great to hear, thanks! I will try the latest versions and report back.

this has been fixed now in the latest versions of SystemJS (0.5.0), (...)

Could you add a tag to github for SystemJS 0.5.0? It makes it easier to manage with bower. Thanks!

[guybedford]

Thanks for reminding me - I've tagged it now.

[renato-zannon]

From my testing, there aren't any issues anymore, so I'm closing this issue.

Thanks for the great work!

[guybedford]

Great to hear that, thanks.