Module naming and declarations

Sam Tobin-Hochstadt samth at
Tue May 7 13:37:51 PDT 2013

On Tue, May 7, 2013 at 4:31 PM, Kevin Smith <zenparsing at> wrote:
>> The whole point of my original email to Andreas is that this doesn't
>> work.  These names are *not* intended to specify where to find the
>> resource.  They *are* intended to be names that different modules can
>> coordinate with.  Should backbone put `import "/js/jquery.js"` in
>> their source file?
> I think we all understand the problem that you're trying to solve here, but
> aren't you putting the cart before the horse?  Can we not design the module
> system first, and then layer packages on top?  Do you not agree that that
> would be a more robust approach?

No, I do not agree. If our module system does not address the use
cases that people have already built JS module systems to solve then
we have failed as stewards of the language.


More information about the es-discuss mailing list