Working circular

In the mean time I can add second parameter to force the full module
On Jul 3, 2014 5:52 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;
>
> I don't think it is obvious. On the one hand I see what you mean, but on
> the other we can't arbitrarily exclude functionality, say if someone found
> a valid use case for ES6 modules to have both being used.
>
> I think we can agree we need to agree on whatever is done here. And right
> now we don't.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/calvinmetcalf/es6-translate/pull/10/files#r14539713>.
>