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

@generative-dom/plugin-events

v0.1.0

Published

Generative DOM plugin — invisible event elements that emit DOM events without rendering

Downloads

80

Readme

@generative-dom/plugin-events

Invisible event-emitting elements for Generative DOM — produce no DOM output.

Installation

pnpm add @generative-dom/plugin-events

Usage

import { GenerativeDom } from '@generative-dom/core';
import { events } from '@generative-dom/plugin-events';

const md = new GenerativeDom(container, { plugins: [events()] });

md.on('progress', (data) => console.log('progress:', data));
md.on('status', (data) => console.log('status:', data));
md.on('milestone', (data) => console.log('milestone:', data));

md.push('<progress value="42" total="100" />\n');
md.push('<status code="ok" message="Done" />\n');
md.push('<milestone name="phase-1" />\n');

Matching

Matches self-closing elements whose tag name is exactly progress, status, or milestone. Any attributes in key="value" format are parsed; numeric values are automatically converted from strings to numbers.

<progress value="50" total="100" />
<status code="running" />
<milestone name="launch" />

Configuration

  • priority: 40 (matched before custom-elements and interactive)
  • level: block (default)
  • matchDescriptor: { startChars: '<' }

Rendered Output

These elements produce no DOM nodes. render() always returns null. Instead, the plugin emits a namespaced event via the plugin context:

  • <progress .../> emits 'progress' with the parsed attribute object
  • <status .../> emits 'status' with the parsed attribute object
  • <milestone .../> emits 'milestone' with the parsed attribute object

Subscribe with generativeDom.on(eventName, handler).