You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The @lit-labs/scoped-registry-mixin package provides a mixin for LitElement that allows a component to choose the custom element tag name for child components it renders in its shadow root, to avoid tag name collisions in the global registry. The implementation is aligned to the Scoped CustomElementRegistry spec proposal; however since that spec is not yet shipped in browsers, it must be used with a scoped CustomElementRegistry polyfill.
We want to collect your feedback on the direction of the @lit-labs/scoped-registry-mixin package as we iterate on it according to our Lit Labs process and move the package towards possible graduation or retirement.
Please try @lit-labs/scoped-registry-mixin and tell us about your experience. Leave comments with your thoughts; highlight what issues or missing features you're blocked on; give a link to a project that uses it; etc.
And so we can have some numbers to look at, you can add reactions to this comment to indicate your experience with this package:
🚀 I have tried this package and it works great. I need it. Ship it!
👍 I have tried this package and it seems like a good idea.
😕 I have tried this package and would use it, but it has serious bugs or missing features.
👀 I am interested, but haven't tried the package yet.
👎 I'm not interested in this package.
Note: other reactions like 😄, 🎉, and ❤️ don't mean anything as part of this scheme. You probably mean, and please use, 🚀, 👍, or 👀.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The
@lit-labs/scoped-registry-mixin
package provides a mixin forLitElement
that allows a component to choose the custom element tag name for child components it renders in its shadow root, to avoid tag name collisions in the global registry. The implementation is aligned to the Scoped CustomElementRegistry spec proposal; however since that spec is not yet shipped in browsers, it must be used with a scoped CustomElementRegistry polyfill.We want to collect your feedback on the direction of the
@lit-labs/scoped-registry-mixin
package as we iterate on it according to our Lit Labs process and move the package towards possible graduation or retirement.Please try
@lit-labs/scoped-registry-mixin
and tell us about your experience. Leave comments with your thoughts; highlight what issues or missing features you're blocked on; give a link to a project that uses it; etc.And so we can have some numbers to look at, you can add reactions to this comment to indicate your experience with this package:
🚀 I have tried this package and it works great. I need it. Ship it!
👍 I have tried this package and it seems like a good idea.
😕 I have tried this package and would use it, but it has serious bugs or missing features.
👀 I am interested, but haven't tried the package yet.
👎 I'm not interested in this package.
Note: other reactions like 😄, 🎉, and ❤️ don't mean anything as part of this scheme. You probably mean, and please use, 🚀, 👍, or 👀.
Beta Was this translation helpful? Give feedback.
All reactions