Caridy Patiño
Caridy Patiño
@domenic this sounds good, I don't see any red-flags. The only detail that I'm not sure is about this: > Nobody has asked for the ability to reflectively construct modules...
@Constellation we haven't talk about this yet. I like to think that we can solve all these with the content type, hinting to the server the capabilities of the browser,...
@matthewp loader allows you to "fetch" any url (it is not opinionated about that), in fact you have the hooks to do whatever you want to produce the final url....
I haven't spent too much time on this topic, but in principle, loader should treat the module scripts as regular scripts, whether they are inline or externals, just like regular...
let's keep in around until we get to this topic.
Few notes (some initial brainstorming): ### Evaluation of arbitrary code Creating a loader and setting the right hooks will effectible allow you to execute any arbitrary code. This needs to...
posting my original answer to the proposal from @guybedford: > I don't think this problem is in the realm of the pipeline, this security measures can be implemented at the...
@domenic this discussion is not really about the "imported" module, it is about parts of the dependency tree that can be executed in turns. E.g.: while doing import A: A...
that is correct!
I don't think this is related to whatwg/html#443. We will be able to introduce execution in turn for any dependency of a top level module imported via script tags without...