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

This thread is a few months old now, and TBH my view has changed somewhat. Now I am starting to think that `<link rel="import">` isn't such a good idea, because it fundamentally duplicates the Javascript `import` statement as a way of managing modules. Basically it unavoidably leads to two parallel module systems. Rather than do that, I think it is better to add a feature to bring HTML in to JS, as was discussed more recently. Then JS modules are the only module system and you can still do what you could do with imports. This is why I favour the "import as" approach. I've got some demo code running here: https://github.com/AshleyScirra/import-as-and-html-modules

I think there's a separate use case for client-side HTML includes, and that was discussed elsewhere.

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