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

nexus-events

v4.0.2

Published

Nexus EventEmitter ==================

Downloads

14

Readme

Nexus EventEmitter

The canonical implementation of EventEmitter is nice, but is has two significant drawbacks:

  • Event handlers are stored in Arrays. Removing a listener requires looping through the array to find the handlers to remove. This makes it unsuitable for frequently adding and removing a large number of event handlers.
  • Event handlers are identified by comparing the references to the underlying function. It makes it very clumsy to use with anonymous functions (or arrow functions).

To correct these two drawbacks, here's my little Yet Another EventEmitter Implementation.

  • Event handlers are stored in Objects, used as maps.
  • Event handlers are referenced by a unique, short string key.
  • Although using Objects as maps is slower than using Arrays, it is actually faster when the number of handlers is large. When its not, then the loss is most often negligible.
  • Bonus: its an ES6 class. You can extend it (although to be honest you can also extend node events.EventEmitter).
  • Bonus 2: if you use Lifespan then you can add a listener using a lifespan, it will be automatically removed when the lifespan is released.

Example

const emitter = new EventEmitter();
let count = 0;
const ln = emitter.on('increase', (n) => count = count + (n || 1));
count.should.be.exactly(0);
emitter.trigger('increase');
count.should.be.exactly(1);
emitter.trigger('increase', 41);
count.should.be.exactly(42);
emitter.off('increase', ln);
emitter.trigger('increase', 100);
count.should.be.exactly(42);
let count2 = 1;
const lifespan = new Lifespan();
emitter.on('multiplyBy', (p) => count2 = count2 * p, lifespan);
count2.should.be.exactly(1);
emitter.trigger('multiplyBy', 2);
count2.should.be.exactly(2);
emitter.trigger('multiplyBy', 4);
count2.should.be.exactly(8);
lifespan.release();
emitter.trigger('multiplyBy', 2);
count2.should.be.exactly(8);

Usage

This module is written in ES6/7. You will need babel to run it.