ModuleImport

Calvin Metcalf calvin.metcalf at gmail.com
Wed Jun 25 05:36:05 PDT 2014


The

    import 'foo'
    let foo = this.get('foo')

Is less of a hassle if you only need it for when you have default and named
exports and need the module object.
 On Jun 25, 2014 7:48 AM, "Kevin Smith" <zenparsing at gmail.com> wrote:

> But if modules were said to have a default default export that was an
>> object with all the exports that could be overridden then that's different.
>>
> I see where you're coming from, and honestly I don't have a better
> argument against a default default.  (I actually tried to argue for that
> once upon a time.)
>
> In any case, I still think the design is not complete unless you have
> *some* way to access the module instance object (even in the case where the
> default has been "overridden"), so we still need ModuleImport.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20140625/9f4dbac2/attachment-0001.html>


More information about the es-discuss mailing list