Caridy Patiño
Caridy Patiño
**Disclaimer: the following is a compilation of many thoughts and discussions about the future of the loader spec, it is not an actual plan, just food for thoughts.** ## Rationale...
[loader.js](https://github.com/caridy/loader.js) implementation feedback
TBD
notes: - during the loading process, we might have clusters of dependencies that are ready to be executed. - order is important for deterministic reasons. - running in multiple turns...
notes: - `` - top level modules (``) - inline imports: (`import "foo";`) - file extension?
notes: - deterministic compilation and execution of multiple `` tags - defer=true by default? - initialization: a module that initializes/configure the loader should block any other import. how? - charset...
From what I can remember, `Reflect.global` was suppose to provide a way to access the global now that `this` is `undefined` in modules, but it is not in the spec...
as today, we only have `loader.import('./foo.js').then(m => {...})`, which is reflective to `import * as m from "./foo.js"`, as we discussed earlier today, we might need to provide reflection for...
YUI-Stockpile supports a custom template to build the combo url thru the loader that does not rely on the `querystring` (few reasons behind that _[1]_). E.g: ``` comboBase: "/combo~", comboSep:...
Disclosure: This issue is just to brainstorm on the proposed linking mechanism and maybe open other avenues. A very common use-case is to have custom elements that should be described...