The `System.loader.import` feature isn't ready for stabilization yet, and
is blocked on a few other pieces of the Loader design. The concerns you
mention are definitely important and we're working on them in the Loader
spec, but no need to rush something through before it's ready. Over time,
we
From: Jason Orendorff [mailto:jason.orendo...@gmail.com]
HostResolveImportedModule is widely implemented by compilers, though
not by browsers. People are writing, using, and sharing ES6 modules today.
So what is your proposal then? Just standardize the node module resolution
algorithm, since
It seems to me that what is needed is something like what used to be
System.get().
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
On Mon, Aug 17, 2015 at 5:02 PM, Domenic Denicola d...@domenic.me wrote:
It's possible to make minor changes to HostResolveImportedModule and
then specify `System.import` in terms of that. [...]
I don't understand. If it's in terms of HostResolveImportedModule, and
HostResolveImportedModule
On Mon, Aug 17, 2015 at 9:50 PM, Bradley Meck bradley.m...@gmail.com wrote:
I think we all want to find a good solution to creating a Loader for ES6
modules. I would follow WHATWG's Loader if you want to participate. There
are a surprising number of considerations, particularly due to existing
From: Jason Orendorff [mailto:jason.orendo...@gmail.com]
Here's what I had in mind:
I have re-read this a few times and still don't understand how you expect this
to be implemented in a standards-compliant way given that
HostResolveImportedModule is not standardized. It doesn't seem to
The problem is timing; WHATWG uses promises, which Node cannot use due to
existing code bases on npm + potential mixing w/ `require`. This causes
time discrepancies and would mean different actions depending on how
exactly hooks are specced out. Node does not want to prevent async loading
on the
On Tue, Aug 18, 2015 at 12:45 PM, Bradley Meck bradley.m...@gmail.com wrote:
This would assume they can support the transformation hooks to do things
like load coffeescript etc. right now, which is the main contention point.
It is a perfectly ordinary occurrence in software to ship some
8 matches
Mail list logo
