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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@litsx/babel-plugin-transform-litsx-scoped-elements

v0.4.7

Published

Transforms LitElement classes to include scoped elements metadata

Readme

@litsx/babel-plugin-transform-litsx-scoped-elements

npm Release Module Provenance

Automatically wires the Litsx DOM mixins for LitElement classes so components can use locally registered custom elements through the shared static elements contract in shadow DOM.

What it does

  • Finds JSX tags that correspond to imported components and rewrites them to kebab-case custom elements.
  • Injects a static elements map with the detected components.
  • Wraps shadow DOM components in ShadowDomMixin, which resolves elements through native or shimmed scoped custom element registries.
  • Wraps static lightDom = true components in LightDomMixin only when they do not require scoped elements.
  • Throws when a component combines light DOM authoring with static elements requirements.
  • Adds the required @litsx/core/elements import only when a component needs a LitSX DOM mixin, keeping untouched classes minimal.
  • Updates matching closing tags and leaves unrelated JSX nodes unchanged.
  • Detects scoped usage inside html tagged template literals as well, ensuring templates converted by the JSX plugin still register components.

Install

npm install --save-dev @litsx/babel-plugin-transform-litsx-scoped-elements
# or
yarn add --dev @litsx/babel-plugin-transform-litsx-scoped-elements

Usage

{
  "plugins": ["@litsx/babel-plugin-transform-litsx-scoped-elements"]
}

Example

Input

import { LitElement, html } from "lit";
import FancyButton from "./FancyButton.js";

class MyElement extends LitElement {
  render() {
    return <FancyButton label="Click" />;
  }
}

Output (simplified)

import { ShadowDomMixin } from "@litsx/core/elements";
import { LitElement, html } from "lit";
import FancyButton from "./FancyButton.js";

class MyElement extends ShadowDomMixin(LitElement) {
  static elements = {
    "fancy-button": FancyButton,
  };

  render() {
    return html`<fancy-button label="Click"></fancy-button>`;
  }
}

Notes

  • Imported and locally declared sibling components can both be collected into static elements.
  • static lightDom = true is a root-mode choice, not a scoped-elements transport. If JSX analysis or authored static elements would require scoped element resolution, the transform fails with a diagnostic.
  • Classes that already wrap the superclass with another mixin still work; the plugin nests the Litsx DOM mixin around the existing expression.
  • The helper pairs nicely with other LitSX transforms such as the JSX-to-template and function-to-class plugins.