matthewwrobb at gmail.com
Tue Aug 18 17:42:16 UTC 2015
It seems to me that what is needed is something like what used to be
In an async environment this should return nothing if it's not already
loaded but in sync environments it could be treated as the imperative API
for sync module loading and go through the same loader steps as
System.import but perhaps with no async wrappers?
- Matthew Robb
On Tue, Aug 18, 2015 at 1:11 PM, Domenic Denicola <d at domenic.me> wrote:
> From: Jason Orendorff [mailto:jason.orendorff at gmail.com]
> > HostResolveImportedModule is widely implemented by compilers, though
> > not by browsers. People are writing, using, and sharing ES6 modules
> So what is your proposal then? Just standardize the node module resolution
> algorithm, since that is what transpilers are doing?
> > It is working, and the people using it have a need for the dynamic API
> to go
> > along with the static syntax, for reasons I pointed out in the initial
> It is not working outside of transpilers, which implement nonstandard
> resolution algorithms. The same transpilers implement JSX, but I don't
> think we'd take that as a reason to say that JSX is "working" and now let's
> start discussing how to standardize a reflective JSX layer.
> es-discuss mailing list
> es-discuss at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss