Matthew Phillips

Maybe there could be an option that allows you to do your own transpiling for each node. Then you could elect not to perform it on the globals.

What would the api look like for that? Maybe something like: ``` js multiBuild({ config: __dirname + "/config.js", main: "main" }, { transpile: function(defaultTranspile, load, outputFormat, options) { if(load.metadata.format ===...

@whitecolor it's pretty easy to work around this. Just any globals mark as amd instead (in system.meta). Then use SystemJS's csp build which includes the script loader. Is there anything...

No, hasn't been picked up by anyone yet.

Yes and no. You can really do anything you want, including customizing the bundling, see the [streams API](http://stealjs.com/docs/steal-tools.guides.streams.html). Doing what you want to do here will take a bit of...

Why is that the best way? What if there was a `module` module in the registry, you'd want to use that rather than the AMD module.

I don't know about easily, but it would be possible. Not sure it's worth the time though.

Does this present a problem some where? I thought all AMD loaders supported the CJS compat syntax, is that wrong?

By default this should only work with strict mode modules. Those that have `"use strict";` at the top of the file. If transpile encounters any module that's not strict mode...

I got this to work for globals using the same technique in systemjs/builder. I see no reason why it has to be System.register though, this will work as a `define`...