Re: [w3c/webcomponents] HTML Modules (#645)

@AshleyScirra your [import-as-and-html-modules](https://github.com/AshleyScirra/import-as-and-html-modules) is a great POC. I would love to get a better idea of what others core members think of this solution. I've been following this thread and no one seems to have much of an opinion about it, especially since a quite a bit of this (not all) solves a similar problem the [dynamic imports proposal](https://github.com/tc39/proposal-dynamic-import) attempts to solve

Offhand, looking at [your use-cases](https://github.com/AshleyScirra/import-as-and-html-modules#use-cases) specifically, I do think it requires the implementor to know a lot about all the different types of API classes that can be passed as the second argument to `importAs()`, especially since certain files can be associated with multiple API classes and certain file extensions can represent different types of content. How would a person know which of these to use without knowing the internals of how the file is evaluated? Has this been a concern?



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/645#issuecomment-391214075