Scoped registry and MWC components #5746
Unanswered
JakobVogelsang
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi all, I am working on an application with a plugin architecture based on the idea of web components. In addition to that we are using mwc components in each of the plugins. We would like to make sure that there are no conflicts with custom tag names and be sure that each plugin is loading the version of the same component we wanted to make use of the custom registry - at the moment still a polyfill, unfortunately.
So far I have see that there are multiple components loading other components like so
which means somehow
customElements.define
is called and the tagsome-component
is registered globally.Does this mean this component library is not designed to be scopable? If so can you recommend a component library with utilizing material design guidlines?
Beta Was this translation helpful? Give feedback.
All reactions