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

Yes, realizing generic imports in static `import` statement has lots of challenges to clear.

But still, plain `import doc from './foo.html' as DocumentFragment` would have values for a way to declare loading dependency to non-JS resources, and gives opportunity for rendering engine or HTTP server for optimizations.  Then, HTML resource will be a simple dumb leaf node, and it is no longer "HTML modules", as it cannot have any dependency without any help of JS code to do processing on it.

So one view of HTML Imports vs HTML modules (the simplified one that only leaf HTML is imported) is that how you see building an web application by defining components and their dependencies in HTML-centric way (HTML Imports) or JS-centric (all in JS `import`) way.

Probably doing plain HTML import is the first step, and then how we hook the loaded resource would be the next step.  We don't have to do it all at once, or all in one feature.

For hook ideas, loader spec already discussed in the past, so before doing it all over again, it's recommended to review what was discussed there.
https://github.com/whatwg/loader/issues/62
https://github.com/whatwg/loader/issues/147

-- 
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-323328247