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

I think exporting element IDs by default will make it difficult to extend the feature later down the line if we do want to make HTML modules export their own dependencies. It's just an extra call to `getElementById` if you have the doc, e.g.:

```js
import doc from "./see-above.html";
const myCustomElementTemplate = doc.getElementById("myCustomElementTemplate");
```

Then we've not locked the feature in to a specific kind of default export that is difficult to change in future.

In other words - how about we ship a basic static import of HTML and see how things pan out from there? I think this was already previously suggested, but this thread is getting a bit long now, it's hard to check...

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

Received on Friday, 5 October 2018 17:09:01 UTC