Static Module Resolution

David Herman dherman at
Sat Jun 30 11:49:22 PDT 2012

On Jun 30, 2012, at 11:46 AM, John J Barton wrote:

> On Sat, Jun 30, 2012 at 11:24 AM, Kevin Smith <khs4473 at> wrote:
> So we have a situation where "legacy.js" must be executed PRIOR TO INITIALIZING "main.js".  This violates the order-of-execution semantics for both ES6 modules and for Node modules (and all "require"-based module systems, for that matter).
> Just define the order of execution between ES6 and pre-ES6 to run legacy.js first. 

Thanks John, you beat me to it -- basically, I agree the interop story isn't worked out enough (in part because when we started working on this there weren't as many dynamic modules around!).

I suspect it might need to be differentiated syntactically, though; I'm not sure there's any way to detect automatically that legacy.js is not an ES6 module but an old-style script. And I'm not sure you *want* to infer that anyway, if the semantics is going to be subtly different.

> Working out the mix and migration strategies is important.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the es-discuss mailing list