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

auto-wc

v0.1.4

Published

Type-safe Web Components with automatic event wiring

Downloads

317

Readme

auto-wc

Tests Size

Type-safe Web Components with automatic event wiring.

The Struggle is Real

"Oh boy! Can't wait setting up listeners again!"

If you've ever written a vanilla Web Component, you know the drill. You create a class, you custom element define it, and then you spend the next 20 minutes writing addEventListener in connectedCallback and removeEventListener in disconnectedCallback. It's repetitive, it's error-prone, and quite frankly, it's boring.

The Old Way (Yawn):

class MyButton extends HTMLButtonElement {
  constructor() {
    super();
    this._handleClick = this._handleClick.bind(this);
  }

  connectedCallback() {
    this.addEventListener('click', this._handleClick);
  }

  disconnectedCallback() {
    this.removeEventListener('click', this._handleClick);
  }

  _handleClick(e) {
    console.log('Clicked!');
  }
}
customElements.define('my-button', MyButton, { extends: 'button' });

The auto-wc Way (Magic!):

defineAutoWebComponent('my-button', 'button', (Base) => class extends Base {
  onClick(e) {
    console.log('Clicked!');
  }
});

Installation

# npm
npm install auto-wc

# pnpm
pnpm add auto-wc

# bun
bun add auto-wc

Or use via CDN:

<script type="module">
  import { defineAutoWebComponent } from 'https://unpkg.com/auto-wc/dist/index.min.js';
</script>

Features

  • Type-safe: Full TypeScript support for DOM events.
  • Automatic Wiring: Methods starting with on (e.g., onClick) are automatically bound to events.
  • Automatic Registration: customElements.define is called automatically.
  • Strict: Event handler properties are read-only to prevent runtime reassignment.
  • Cleanup: Event listeners are automatically removed on disconnect.
  • Zero Dependencies: Lightweight and fast.

Usage

TypeScript / ES Modules

import { defineAutoWebComponent } from "auto-wc";

defineAutoWebComponent(
  "my-button",
  "button",
  (Base) =>
    class extends Base {
      // ...
    }
);

Full Example

import { defineAutoWebComponent } from "auto-wc";

defineAutoWebComponent(
  "my-button",
  "button",
  (Base) =>
    class extends Base {
      // Automatically wired to 'click' event
      onClick(e: MouseEvent) {
        console.log("Button clicked!");
      }

      // Automatically wired to 'dblclick' event
      onDblClick(e: MouseEvent) {
        console.log("Double clicked!");
      }

      // Standard lifecycle methods work as expected
      connectedCallback() {
        super.connectedCallback();
        console.log("Connected");
      }
    },
  { observedAttributes: ["disabled"] },
);

HTML Usage (is="" directive)

Since this library creates customized built-in elements, you must use the is attribute on the extended standard HTML element:

<!-- Correct -->
<button is="my-button">Click Me</button>

<!-- Incorrect (won't work for built-in extends) -->
<my-button>I will never work!</my-button>

API

defineAutoWebComponent(tagName, extendsTag, factory, options)

  • tagName: The custom element tag name (e.g., 'my-button').
  • extendsTag: The HTML tag to extend (e.g., 'button', 'div').
  • factory: A function that receives the Base class and returns your implementation.
  • options: Optional configuration object.
    • observedAttributes: Array of attribute names to observe.

This function automatically calls customElements.define with the provided tagName and the generated class.

License

MIT