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

rad-event-listeners

v1.1.0

Published

Utility to add multiple event listeners

Readme

rad-event-listeners

Utility to add multiple event listeners, which can be individually removed, or all at once.

Also provides a signal that aborts on reentry, to help clean up processes set up in the event listener.

Inspired by rad-event-listener and @remix-run/interaction.

Usage

import { radEventListeners } from "rad-event-listeners";

const unsub = radEventListeners(
  window,
  {
    // signal aborts when next click event is fired
    click: (ev, signal) => console.log(ev, signal),
    keydown: [
      {
        handleEvent: (ev, signal) => console.log(ev, signal),
      },
      // Event options
      { once: true },
    ],
  },
  // Global options
  { passive: true },
);

unsub.click();
unsub();

rads

An alternative API, which passes the addEventListener function to a callback, and only returns a single unsubscribe function.

import { rads } from "rad-event-listeners";

const unsub = rads(
  window,
  (add) => {
    add("click", (ev) => console.log(ev));
    add("keydown", (ev) => console.log(ev), { once: true });
  },
  { passive: true },
);

// no individual unsubs
unsub();

Requirements

This uses AbortSignals (and specifically AbortSignal.any) to manage event listener removal. Check the MDN docs for browser/environment support.

Typescript

Similarly to rad-event-listener, this library attempts to infer the event types from the event target, using the on${EventName} properties.

If you're using a target that doesn't specify these properties, all event names will be allowed, and the event type will default to Event. You can then specify the event type manually.

import { radEventListeners } from "rad-event-listeners";

const unsub = radEventListeners(customTarget, {
  // This will default the event type to Event
  something(ev) {
    console.log(ev);
  },
  // but you can specify it manually
  custom(ev: CustomEvent) {
    console.log(ev.detail);
  },
});

Alternatively, use the rads function, which doesn't attempt to infer the event types.

import { rads } from "rad-event-listeners";

const unsub = rads(customTarget, (add) => {
  add("something", (ev) => console.log(ev));
  // because this is the original addEventListener function, it'll use whatever type the target specifies
  add("custom", (ev) => console.log(ev.detail));
});