npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@lit-labs/scoped-registry-mixin

v1.0.3

Published

A mixin for using speculative "scoped CustomElementRegistry" with LitElement.

Downloads

5,949

Readme

@lit-labs/scoped-registry-mixin

ScopedRegistryHost mixin for LitElement that integrates with the speculative Scoped CustomElementRegistry polyfill.

🚨 Warning: Scoped Custom Element Registries is a proposed browser API. It has not been finalized nor shipped in any browser. This mixin is provided to evaluate the proposal and facilitate feedback. Use this feature, and the polyfill in production code at your own risk.

Overview

The Scoped Custom Element Registries WICG proposal introduces new APIs for scoping custom element definitions to shadow roots, such that the mapping of tag names to custom element class doesn't rely on a single global registry.

When new elements are created within a shadow root with a scoped custom element registry, the browser will use the scoped registry rather than the global registry to look up custom element definitions. When using a scoped element registry, all used custom element elements must be defined within that scope.

ScopedRegistryHost adds the following features to LitElement:

  1. Automatically creates a scoped CustomElementRegistry for the class
  2. Provides sugar for defining custom elements in the scoped registry
  3. Passes the registry to attachShadow() to enable scoping
  4. Passes the shadow root to lit-html to create DOM within the scope

A speculative Scoped CustomElementRegistry polyfill is being developed. Because the proposal is not implemented natively, ScopedRegistryHost requires the polyfill.

Usage

The mixin adds a declarative static elementDefinitions property for declaring the custom elements to be scoped locally to its Shadow DOM.

Basic usage is as follows:

import {LitElement, html} from 'lit';
import {ScopedRegistryHost} from '@lit-labs/scoped-registry-mixin';

import {SimpleGreeting} from './simple-greeting.js';

class ScopedComponent extends ScopedRegistryHost(LitElement) {
  // Elements here will be registered against the tag names provided only
  // in the shadow root for this element
  static elementDefinitions = {
    'simple-greeting': SimpleGreeting,
  };

  render() {
    return html` <simple-greeting
      id="greeting"
      name="scoped world"
    ></simple-greeting>`;
  }
}

Contributing

Please see CONTRIBUTING.md.