Re: [w3c/webcomponents] HTML Modules: multiple scripts exporting same named export (#831)

I can add a note clarifying scenario to that spec/explainer doc.  I suppose that the pseudocode implies this behavior, but it is by no means obvious (at least to me) even in my JS-module-only example above that things should fail only if a conflicting export is actually imported at some point.

Being stricter than the spec seems reasonable here.  I assume SystemJS differs from the native JavaScript module behavior in the same way?  If it isn't a problem for JS modules then I don't expect that it would be a problem for HTML modules.

-- 
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/831#issuecomment-526398002