The ES Loader does not maintain a dependency tree. It maintains a table of names->modules. So when the @import rules mutate, just load the new names. Any new modules will be traversed for dependents and new name->modules entries will be created. Well, assuming you figure out how to integrate CSS parsing for dependents.
jjb On Fri, Aug 15, 2014 at 3:24 PM, Ian Hickson <[email protected]> wrote: > > ES6 modules are immutable, but some things on the Web platform that might > have dependencies can have those dependencies change over time. For > example, CSS style sheets have a mutable object model, and one of the > things in that object model is their list of @imports, so you can > dynamically change a style sheet's dependencies. > > Assuming we are implementing all CSS loads through the ES6 module loader > system, what's the appropriate way in which I should spec reactions to > changes to a CSS object's @import rules? > > -- > Ian Hickson U+1047E )\._.,--....,'``. fL > http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. > Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.' > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
