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

In practice, it is convenient to adhere to the agreement on the naming of custom tags and their accessibility at url address.

Then this is one rule for many custom tags, which can be expressed in one loader JS modules
```JavaScript

// For many internal components
customElements.defineLazy('*', tagName => import(`/modules/${tagName}.js`));

// For many external components
customElements.defineLazy('vendor-*', tagName => import(`https://vendor.com/src/${tagName}.js`));

```

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