Working circular

Yeah I'd wait to see how the next tc39 meeting shakes out, but if systemjs
isn't doing something like this it probably should,  it does occur to me
that I can likely static analyze a good portion of the names exports so if
it remains legal to do both I can export them as well.
On Jul 3, 2014 5:32 PM, "Guy Bedford" <notifications@github.com> wrote:

> In lib/evaluate.js:
>
> > +  // this can also be done with VM or something cleaner
> > +  scopedEval.call(global, global, localRequire, localModule, record.exports, record.address, record.dirname);
> > +}
> > +
> > +function ourRequire(name, loader) {
> > +  // if in the side table
> > +  if (sidetable.has(name)) {
> > +    var record = sidetable.get(name);
> > +    evaluate(name, loader);
> > +    return record.exports;
> > +  }
> > +
> > +  if (loader.has(name)) {
> > +    var mod = loader.get(name);
> > +    if ('default' in mod) {
> > +      return mod.default;
>
> An ES6 module exporting only a default property here would be loaded
> directly in CommonJS.
>
> I suppose this concerns the recent es-discuss discussions as well actually.
>
> We could potentially make this behaviour the standard. But we'd need to
> agree, because we can't have SystemJS doing one thing and this project
> doing another!
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/calvinmetcalf/es6-translate/pull/10/files#r14538978>.
>