Option to configure module output about builder

[guybedford]

Instantiate is the default because it supports ES6 bindings and circular references, which is a feature integrated into the core of SystemJS.

I know it sounds strange, but the edge case features (circular references) determine the workflow.

That said yes you can compile to AMD or CommonJS. You could use the traceur --dir compile option to compile everything into AMD before using this builder, or we could look at adding it as an option as well.

[guybedford]

Is this still a feature you are after? Perhaps have a look at the upcoming bundle-sfx function in the next jspm release to reassess.

[OliverJAsh]

@guybedford Does this also cover jspm/jspm-cli#75?

[guybedford]

Yes exactly. It's not AMD / CJS transpiling but a self-executing bundling system.

[outdooricon]

@guybedford I think that this hints at a need in the Builder... What I'm encountering is needing to run Traceur for the normal es6 transpiling of other non-module es6 functionality, before running systemjs-builder. It seems odd to have Traceur running in two steps, instead of allowing commands to be passed from the Builder through to Traceur (like allowing an option to trigger the normal es6 transpiling).

[guybedford]

@outdooricon can you explain why you need to separately run Traceur for normal es6 transpiling?

[outdooricon]

At one point I had encountered something in es6 that wasn't getting transpiled through the builder. This led me to believe that the builder sidestepped transpiling anything other than modules. However, now switching back to just using the builder, I can't seem to find what that was... So it looks like my use case just disappeared.

[guybedford]

I'd be interested to hear what wasn't transpiling. Glad to hear it's working out though.

[outdooricon]

If I find it again, I'll bring it up