js-loaders
js-loaders copied to clipboard
jorendorff
Pseudoimplementation of the proposed ES6 module loaders.
1. Let binding be the result of calling the ResolveExport abstract operation passing def.[[Module]] and def.[[ImportName]] as arguments. Needs to pass visited too.
In LinkDeclarativeModules ( loads, loader ), step 3.c.iv.1 1. Let module be the result of calling the LoaderRegistryLookup abstract operation with arguments loader and normalizedName.
Historically eval() has been difficult to support in development tools because the source name is not defined. Typically (bad) choice is to assign the source to the name of the...
The current API is curiously missing a function to dynamically load source but evaluate it as Script. Loader.import(name): fetch name, parse as module, Loader.define(name, source): parse 'source' as module, Loader.missingFeature(name):...
All the productions in the spec have "Runtime Semantics: Evaluation" which includes speccing what the completion value is.
A meta-suggestion: adopt 'normalizeName' or similar for names that are already or are expected to be normalized. Or adopt 'moduleSpecifier' or similar for names that are not normalized. 'name' is...
Nobody's terribly fond of the ondemand table. What if instead: ``` System.ondemand = {"*": "*.js"}; // this is the default System.ondemand = { "jquery": "/scripts/jquery-1.9.1.min.js", "dherman/*": "https://github.com/dherman/*.js", "ember/*": "/scripts/ember.js" };...
Surely URL fragments should be excluded from the default baseURL of the current page?
Looking at the System API, we have `get` and `set`, based on the module name and it seems that the module registry itself is completely internal. In various scenarios, it's...
As far as I can understand, `Loader.prototype.load` will load a module, link it, and populate in the module table, but without executing it? Does this mean that the use case...
Metadata
Owner
Metadata
Pseudoimplementation of the proposed ES6 module loaders.