whatwg/loader

Issues

• Is this spec living?

  #159 opened 7 years ago by foolip
  6

• Peeling out import()

  #149 opened 7 years ago by domenic
  15

• Make importing fail if URL has changed (for SPA, PJAX, and History API)

  #158 opened 7 years ago by falsandtru
  1

• Progress events

  #143 opened 8 years ago by jhnns
  3

• [Discussion] Simplification of Loader

  #147 opened 8 years ago by caridy
  45

• Idea: Add Header to Identify imported names

  #156 opened 7 years ago by Jamesernator
  4

• Clarify Milestones/Roadmap

  #153 opened 7 years ago by indolering
  1

• Safely hooking the loader of an iframe

  #155 opened 8 years ago by andyearnshaw
  2

• § 2.3. Promises: "promises guide" should be a hyperlink

  #154 opened 8 years ago by mk-pmb
  0

• Edge implementation status changed

  #151 opened 8 years ago by raphaelokon
  1

• It should be possible to synchronous retrieve a "loaded and ready" module's export object

  #130 opened 9 years ago by concavelenz
  7

• Per module-script tree information

  #148 opened 8 years ago by Constellation
  2

• Execution hook

  #146 opened 8 years ago by guybedford
  0

• PreEvaluate/PostEvaluate stages

  #142 opened 8 years ago
  8

• Looking back instead of looking forward?

  #141 opened 8 years ago by robbie-mac
  8

• Mention code of conduct in README

  #135 opened 8 years ago by annevk
  1

• [bug] `referrer` in `Loader.import()` is passed down to `Resolve()` abstract, where is it being tested as string in step 3.

  #105 opened 9 years ago by caridy
  1

• Fetch response metadata

  #132 opened 8 years ago by nlwillia
  1

• Importing JSON files?

  #133 opened 8 years ago by beck
  2

• Relative module URLs starting without "./"

  #131 opened 8 years ago by bangseongbeom
  3

• How are named exports passed to hooks when Loader.import is called?

  #128 opened 9 years ago by RGBboy
  6

• [question] `Instantiation(loader, result, source)` will assume `result` is callable in step 3, but `result` is just an exotic namespace object that is not callable.

  #115 opened 9 years ago by caridy
  5

• [follow up] issue #46 adds an extra step to set [[Realm]] on the module

  #118 opened 9 years ago by caridy
  1

• [bug][question] step 14. [Set O’s [[Module]] internal slot to module.] in ModuleStatus constructor should not set the internal slot to module if it can be a promise as described in step 9.

  #114 opened 9 years ago by caridy
  2

• [bug][important] step 6.c.i. [Let status be ? ExtractDependencies(entry, optionalInstance, source).] in RequestInstantiate should bypass `optionalInstance.[[Module]]` instead of just `optinoalIstance`.

  #113 opened 9 years ago by caridy
  2

• [suggestion] Step [12. Set mod.[[Namespace]] to ns.] in `Module()` seems to be redundant because step 9 in 9.4.6.13 ModuleNamespaceCreate (module, exports) in 262 will do that.

  #111 opened 9 years ago by caridy
  1

• [question] step [4.a. Assert: instance is a Source Text Module Record.] in 6.1.3. ExtractDependencies seems to be bold. Not only source text module records can have dependencies.

  #112 opened 9 years ago by caridy
  1

• [bug] `Module()` should validate first argument `descriptors` before calling `ParseExportsDescriptors`.

  #108 opened 9 years ago by caridy
  2

• [Question] `Instantiation()` returns after calling `ParseModule(source)` without setting the `[[Realm]]`, is that ok? Or is the realm only needed if result is callable?

  #107 opened 9 years ago by caridy
  2

• [suggestion] `RequestSatisfy()` calls `RequestInstantiate()` that resolves to a `optionalInstance`, but that's really not used at all outside of `RequestInstantiate()`, we might just resolve to the entry itself.

  #106 opened 9 years ago by caridy
  1

• [bug] `ModuleStatusConstructor()`: argument `module` is optional but it is being tested in step 5 and 6.

  #104 opened 9 years ago by caridy
  1

• [bug] `Module()` calls `ModuleNamespaceCreate(mod, realm, exportNames)`, but [[Realm]] is just an internal slot of mod, and `ModuleNamespaceCreate()` is not expecting that.

  #109 opened 9 years ago by caridy
  1

• [discussion] `class Module` 3rd argument `evaluate` is optional, but it seems to be required by `ModuleEvaluation()` when evaluating the module.

  #110 opened 9 years ago by caridy
  2

• Question: which objects will be exposed onto the window / global?

  #125 opened 9 years ago by joeldenning
  2

• Handling of symlinks / redirects

  #124 opened 9 years ago by guybedford
  4

• How should the loader impact <script type="module">?

  #121 opened 9 years ago by domenic
  10

• [discussion] deterministic execution in turns

  #85 opened 9 years ago by caridy
  7

• Question about interaction with TopLevelModuleEvaluationJob

  #99 opened 9 years ago by jonco3
  1

• [task] milestone 0: name resolution

  #84 opened 9 years ago by caridy
  1

• make it possible to manually cancel preceding pipeline stages

  #89 opened 9 years ago by dherman
  7

• [bug] 8.2.6. ModuleEvaluation() is assuming `this.[[Evaluate]]`, it should be `this.[[Module]].[[Evaluate]]` because it doesn't hold the evaluate internal slot directly.

  #116 opened 9 years ago by caridy
  1

• Provide / install

  #117 opened 9 years ago by matthewp
  2

• Loader.prototype.load to take resolved key as input

  #103 opened 9 years ago by guybedford
  1

• What's the status of the level 0 spec?

  #101 opened 9 years ago by jonco3
  4

• Proposal: CSP-compatible hooks

  #100 opened 9 years ago by guybedford
  6

• Import non-JS code from the import declaration

  #87 opened 9 years ago by Constellation
  5

• GetRegistryEntry defines name 'result' twice

  #98 opened 9 years ago by jonco3
  3

• registry refactoring

  #96 opened 9 years ago by dherman
  14

• pipeline state bugs

  #88 opened 9 years ago by dherman
  3

• [Refactor] Formalizing RegistryEntry Objects

  #95 opened 9 years ago by caridy
  1