Re: [w3c/webcomponents] Lazy Custom Element Definitions (#782)

@trusktr you are absolutely right, this is a bit of a hazard. This is also a hazard with dynamic import in general.

The key here though is to allow dependents to specify that they can deal with async loading of a definition, which then allows flexibility for tools like bundlers. An app may still combine multiple lazy loaded components in the same bundle... I've seen proposed systems for doing this dynamically / statistically based on usage or analyzing the content to be served.

-- 
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/782#issuecomment-562369236