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

event-registry

v0.3.0

Published

Keeps track of EventEmitter listeners and automatically removes them upon selected events.

Downloads

150

Readme

event-registry

npm Dependencies Build Status Coverage Status JavaScript Standard Style

Keeps track of EventEmitter listeners and automatically removes them upon selected events. Useful when you want to avoid EventEmitter memory leaks caused by listeners not being removed.

Usage

const EventRegistry = require('event-registry')

const eventRegistry = new EventRegistry()
const emitter = getSomeEventEmitter()
const otherEmitter = getSomeOtherEventEmitter()

// Attach a listener using EventEmitter.prototype.on and remember it.
eventRegistry.on(emitter, 'data', someDataListener)

// Attach a one-off listener using EventEmitter.prototype.on and remember it.
eventRegistry.once(emitter, 'end', someEndListener)

// A single registry can track any number of event emitters.
eventRegistry.on(otherEmitter, 'progress', someProgressListener)

// When the 'end' event is emitted, remove all remembered listeners.
// Note that this will also remove the progress listener from otherEmitter.
eventRegistry.fin(emitter, 'end')

API

EventEmitter Proxies

An EventRegistry proxies the following functions to the emitter:

  • addListener(emitter, event, listener) AKA on(emitter, event, listener)
  • once(emitter, event, listener)
  • removeListener(emitter, event, listener)
  • removeAllListeners(emitter, [event])

Additionally, it keeps track of every listener passed. When a final event occurs (see below), it will remove all of these listeners.

Final Events

fin(emitter, event)

Marks the given event on the emitter as final. When that event occurs, all listeners will be removed.

unfin(emitter, event)

Undoes a call to fin. Marks the event on the emitter as non-final.

onceFin(emitter, event, listener)

Shorthand for once(emitter, event, listener) followed by fin(emitter, event). Saves you a statement in this common scenario.

clear()

Removes all attached listeners and marks all final events as non-final. Basically what happens when a final event is emitted.

Author

Tim De Pauw

License

MIT