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

eventti

v4.0.0

Published

A predictable event emitter for pragmatists, written in TypeScript.

Downloads

40

Readme

Eventti

A predictable event emitter for pragmatists, written in TypeScript.

  • 🔮 Predictable behaviour.
  • 🎯 Hits the sweet spot between features, size and performance.
  • 🎁 Small footprint (well under 1kB gzipped).
  • ⚡ Highly optimized and stable performance across browsers.
  • 🤖 Extensively tested.
  • 🍭 No runtime dependencies, what you see is what you get.
  • 💝 Free and open source, MIT Licensed.

Why another event emitter?

Devs just love to write their own event emitters, don't they? 🙋‍♂️ I've been guilty of writing a few myself, and I've also used many existing implementations of which there certainly is no shortage of.

However, there's always been one aspect that irks me in most of them, and that's the handling of duplicate event listeners. It's inconsistent. In some implementations duplicate listeners are not allowed (and they might be just silently ignored) while in others they are allowed, but then you can't remove a specific listener anymore, because you don't know which one of the duplicates you're removing. Depending on the implementation it might be the first, last or all matching listeners.

// A very contrived example, but you get the point.
const ee = new YetAnotherEventEmitter();
let counter = 1;
const increment = () => void counter += 1;
const square = () => void counter *= counter;
ee.on('test', increment);
ee.on('test', square);
ee.on('test', increment);
ee.off('test', increment); // 🎲
ee.emit('test'); // counter === 1 or 2 or 4

To rectify this flaw in API design, Eventti follows in the footsteps of setTimeout()/clearTimeout() (and other similar Web APIs) by assigning and returning a unique id for each listener. No more guessing which listener you're removing.

const eventti = new Eventti();
let counter = 1;
const increment = () => void counter += 1;
const square = () => void counter *= counter;
const id1 = eventti.on('test', increment);
const id2 = eventti.on('test', square);
const id3 = eventti.on('test', increment);
eventti.off('test', id3); // ✅
eventti.emit('test'); // counter === 4

Additionally, you can provide the listener id manually and define strategy for handling duplicate ids. This is especially useful when you want to update an existing listener with a new one without changing it's index in the listener queue.

const eventti = new Emitter({ dedupe: 'update' });
eventti.on('test', () => console.log('foo'), 'idA');
eventti.on('test', () => console.log('bar'), 'idB');
// Update the listener for idA.
eventti.on('test', () => console.log('baz'), 'idA');
eventti.emit('test');
// -> baz
// -> bar

Finally, I hope this is the last event emitter I'll ever need to write 🤞.

Performance

Regarding performance, Eventti is fine-tuned to be as fast as possible with the feature set it provides.

Listeners and their ids are stored in a Map<id, listener> instead of an array (the common convention), due to which Eventti loses a bit in performance when it comes to adding listeners. It's hard to beat a simple array.push().

However, emitting speed is on par with the fastest of emitters due to an optimization Eventti applies: the listeners are cached in an array, which is invalidated any time a listener is removed. This way we don't have to always clone the listeners on emit, most of the time we can go straight to looping the cached array.

Where things get interesting is when we start removing listeners. While most emitters need to loop an array of listeners to find the matching listener(s), Eventti can just delete the listener from the Map by the listener id. This is a huge performance boost when you have a lot of listeners.

In practice, Eventti and most other emitters are so fast that you don't need to worry about performance. But if you're interested in the numbers, we have some benchmarks, which you can run with npm run test-perf.

Getting started

The library is provided as an ECMAScript module (ESM), a CommonJS module (CJS) and as an IIFE bundle.

Node

npm install eventti
import { Emitter } from 'eventti';
const emitter = new Emitter();

Browser

<script type="importmap">
  {
    "imports": {
      "eventti": "https://cdn.jsdelivr.net/npm/[email protected]/dist/index.js"
    }
  }
</script>
<script type="module">
  import { Emitter } from 'eventti';
  const emitter = new Emitter();
</script>

Usage

import { Emitter } from 'eventti';

// Define emitter's events (if using TypeScript).
// Let the key be the event name and the value
// be the listener callback signature.
type Events = {
  a: (msg: string) => void;
  b: (str: string, num: number) => void;
};

// Create an emitter instance.
const emitter = new Emitter<Events>();

// Add listeners to events.
const idA = emitter.on('a', (msg) => console.log(msg));
const idB = emitter.on('b', (...args) => console.log(...args));

// Add a one-off listener to an event.
emitter.once('a', (msg) => console.log('once: ' + msg));

// Emit events.
emitter.emit('a', 'foo');
// -> foo
// -> once: foo
emitter.emit('a', 'foo');
// -> foo
emitter.emit('b', 'bar', 5000);
// -> bar 5000

// Count event listeners.
emitter.listenerCount('a'); // -> 1

// Count all listeners.
emitter.listenerCount(); // -> 2

// Remove listeners.
emitter.off('a', idA);
emitter.off('b', idB);

Listener ids and dedupe modes

The founding feature of Eventti is that every listener is assigned with a unique id. The id can be any value except null or undefined. By default Eventti uses Symbol() to create unique ids, but you can provide your own function if you want to use something else and you can also provide the id manually via .on() and .once() methods.

Now the question is, what should happen when you try to add a listener with an id that already exists? Well, it's up to you and Eventti allows you to choose from four different options what the behaviour should be.

dedupe: "add"

When the dedupe is set to "add" (which it is by default) the existing listener (matching the id) will be first completely removed and then the new listener will be appended to the listener queue.

import { Emitter, EmitterDedupe } from 'eventti';

const emitter = new Emitter({ dedupe: EmitterDedupe.ADD });

emitter.on('a', () => console.log('foo 1'), 'foo');
emitter.on('a', () => console.log('bar'), 'bar');
emitter.on('a', () => console.log('foo 2'), 'foo');

emitter.emit('a');
// -> bar
// -> foo 2

dedupe: "update"

When the dedupe is set to "update" the existing listener (matching the id) will be replaced with new listener while keeping the listener at the same index in the listener queue.

import { Emitter, EmitterDedupe } from 'eventti';

const emitter = new Emitter({ dedupe: EmitterDedupe.UPDATE });

emitter.on('a', () => console.log('foo 1'), 'foo');
emitter.on('a', () => console.log('bar'), 'bar');
emitter.on('a', () => console.log('foo 2'), 'foo');

emitter.emit('a');
// -> foo 2
// -> bar

dedupe: "ignore"

When the dedupe is set to "ignore" the new listener is simply ignored.

import { Emitter, EmitterDedupe } from 'eventti';

const emitter = new Emitter({ dedupe: EmitterDedupe.IGNORE });

emitter.on('a', () => console.log('foo 1'), 'foo');
emitter.on('a', () => console.log('bar'), 'bar');
emitter.on('a', () => console.log('foo 2'), 'foo');

emitter.emit('a');
// -> foo 1
// -> bar

dedupe: "throw"

When the dedupe is set to "throw" an error is thrown.

import { Emitter, EmitterDedupe } from 'eventti';

const emitter = new Emitter({ dedupe: EmitterDedupe.THROW });

emitter.on('a', () => console.log('foo 1'), 'foo');
emitter.on('a', () => console.log('bar'), 'bar');
emitter.on('a', () => console.log('foo 2'), 'foo'); // throws an error

Changing dedupe mode

You can change the dedupe mode at any point after instantiaiting the emitter. Just directly set the mode via emitter's dedupe property.

import { Emitter, EmitterDedupe } from 'eventti';

const emitter = new Emitter();

emitter.dedupe = EmitterDedupe.THROW;

Tips and tricks

Mimicking the classic event emitter API

Eventti's API is a bit different from most other event emitters, but you can easily mimic the classic API (where you remove listeners based on the callback) by using the getId option. This way you can use the listener callback as the listener id by default and remove listeners based on the callback. But do note that this way duplicate listeners can't be added, which may or may not be what you want.

import { Emitter } from 'eventti';

const emitter = new Emitter({
  // Decide what to do with duplicate listeners by default.
  dedupe: 'throw',
  // Use the listener callback as the listener id.
  getId: (listener) => listener,
});

const listener = () => {};

// Now the listener callback is used as
// the listener id automatically...
const idA = emitter.on('a', listener);
console.log(idA === listener); // -> true

// ...and you can remove the listener
// with the listener callback...
emitter.off('a', listener);

// ...and duplicate listeners can't be added.
emitter.on('a', listener);
emitter.on('a', listener); // throws an error

Ergonomic unbinding

Eventti's API is designed to be explicit and predictable, but sometimes you might want a bit more ergonomic API by returning a function from the .on() and .once() methods which you can use to unbind the listener.

Here's a recipe for that:

import { Emitter, Events, EventListenerId, EmitterOptions } from 'eventti';

class ErgonomicEmitter<T extends Events> extends Emitter<T> {
  constructor(options?: EmitterOptions) {
    super(options);
  }

  on<EventName extends keyof T>(
    eventName: EventName,
    listener: T[EventName],
    listenerId?: EventListenerId,
  ): EventListenerId {
    const id = super.on(eventName, listener, listenerId);
    return () => this.off(eventName, id);
  }

  once<EventName extends keyof T>(
    eventName: EventName,
    listener: T[EventName],
    listenerId?: EventListenerId,
  ): EventListenerId {
    const id = super.once(eventName, listener, listenerId);
    return () => this.off(eventName, id);
  }
}

const emitter = new ErgonomicEmitter();
const unbind = emitter.on('a', () => console.log('foo'));
unbind(); // removes the listener

Do note that this breaks the API contract as now you can't use the return value of .on() and .once() methods anymore to remove the listeners with .off method. But if you're okay with that, this is a nice way to make the API more ergonomic.

Emitter API

Emitter is a class which's constructor accepts an optional EmitterOptions object with the following properties:

  • dedupe
    • Defines how a duplicate event listener id is handled:
      • "add": the existing listener (of the id) is removed and the new listener is appended to the event's listener queue.
      • "update": the existing listener (of the id) is replaced with the new listener without changing the index of the listener in the event's listener queue.
      • "ignore": the new listener is silently ignored and not added to the event.
      • "throw": as the name suggests an error will be thrown.
    • Accepts: EmitterDedupe.
    • Optional, defaults to "add" if omitted.
  • getId
    • A function which is used to get the listener id for a listener callback. By default Eventti uses Symbol() to create unique ids, but you can provide your own function if you want to use something else. Receives the listener callback as the first (and only) argument.
    • Accepts: (listener: EventListener) => EventListenerId.
    • Optional, defaults to () => Symbol() if omitted.
import { Emitter, EmitterDedupe } from 'eventti';

// Define emitter's events (if using TypeScript).
// Let the key be the event name and the value
// be the listener callback signature.
type Events = {
  a: (msg: string) => void;
  b: (str: string, num: number) => void;
};

// Create emitter instance.
const emitterA = new Emitter<Events>();

// Create emitter instance with options.
let _id = Number.MIN_SAFE_INTEGER;
const emitterB = new Emitter<Events>({
  dedupe: EmitterDedupe.THROW,
  getId: () => ++_id,
});

// You can read and modify the `dedupe` setting
// freely. It's okay to change it's value whenever
// you want.
emitterB.dedupe; // -> "throw"
emitterB.dedupe = EmitterDedupe.IGNORE;

// You can read and modify the `getId` setting freely.
// It's okay to change it's value whenever you want.
emitterB.getId = () => Symbol();

Methods

emitter.on()

Add a listener to an event.

Syntax

emitter.on( eventName, listener, [ listenerId ] )

Parameters

  1. eventName
    • The name of the event you want to add a listener to.
    • Accepts: EventName.
  2. listener
    • A listener function that will be called when the event is emitted.
    • Accepts: EventListener.
  3. listenerId
    • The id for the listener. If not provided, the id will be generated by the emitter.getId function.
    • Accepts: EventListenerId.
    • optional

Returns

A listener id, which can be used to remove this specific listener. Unless manually provided via arguments this will be whatever the emitter.getId method spits out, and by default it spits out symbols which are guaranteed to be always unique.

Examples

import { Emitter } from 'eventti';

const emitter = new Emitter();

const a = () => console.log('a');
const b = () => console.log('b');

// Bind a and b listeners to "test" event. Here we don't provide the third
// argument (listener id) so it is created automatically and returned by the
// .on() method.
const id1 = emitter.on('test', a);
const id2 = emitter.on('test', b);

// Here we bind a and b listeners agains to "test" event, but we provide the
// listener id manually.
const id3 = emitter.on('test', a, 'foo');
const id4 = emitter.on('test', b, 'bar');
id3 === 'foo'; // => true
id4 === 'bar'; // => true

emitter.emit('test');
// a
// b
// a
// b

emitter.off('test', id2);
emitter.emit('test');
// a
// a
// b

emitter.off('test', a);
emitter.emit('test');
// b

emitter.once()

Add a one-off listener to an event.

Syntax

emitter.once( eventName, listener, [ listenerId ] )

Parameters

  1. eventName
    • The name of the event you want to add a listener to.
    • Accepts: EventName.
  2. listener
    • A listener function that will be called when the event is emitted.
    • Accepts: EventListener.
  3. listenerId
    • The id for the listener. If not provided, the id will be generated by the emitter.getId function.
    • Accepts: EventListenerId.
    • optional

Returns

A listener id, which can be used to remove this specific listener. Unless manually provided via arguments this will be whatever the emitter.getId method spits out, and by default it spits out symbols which are guaranteed to be always unique.

Examples

import { Emitter } from 'eventti';

const emitter = new Emitter();
const a = () => console.log('a');
const b = () => console.log('b');

emitter.on('test', a);
emitter.once('test', b);

emitter.emit('test');
// a
// b

emitter.emit('test');
// a

emitter.off()

Remove an event listener or multiple event listeners. If no listenerId is provided all listeners for the specified event will be removed. If no eventName is provided all listeners from the emitter will be removed.

Syntax

emitter.off( [ eventName ], [ listenerId ] );

Parameters

  1. eventName
    • The name of the event you want to remove listeners from.
    • Accepts: EventName.
    • optional
  2. listenerId
    • The id of the listener you want to remove.
    • Accepts: EventListenerId.
    • optional

Examples

import { Emitter } from 'eventti';

const emitter = new Emitter();

const a = () => console.log('a');
const b = () => console.log('b');

const id1 = emitter.on('test', a);
const id2 = emitter.on('test', b);
const id3 = emitter.on('test', a);
const id4 = emitter.on('test', b);

// Remove specific listener by id.
emitter.off('test', id2);

// Remove all listeners from an event.
emitter.off('test');

// Remove all listeners from the emitter.
emitter.off();

emitter.emit()

Emit events.

Syntax

emitter.emit( eventName, [ ...args ] )

Parameters

  1. eventName
    • The name of the event you want to emit.
    • Accepts: EventName.
  2. ...args
    • The arguments which will be provided to the listeners when called.
    • Accepts: any.
    • Optional.

Examples

import { Emitter } from 'eventti';

const emitter = new Emitter();

emitter.on('test', (...args) => console.log(args.join('-')));

// Provide arguments to the event's listeners.
emitter.emit('test', 1, 2, 3, 'a', 'b', 'c');
// '1-2-3-a-b-c'

emitter.listenerCount()

Returns the listener count for an event if eventName is provided. Otherwise returns the listener count for the whole emitter.

Syntax

emitter.listenerCount( [ eventName ] )

Parameters

  1. eventName
    • The name of the event you want to get the listener count for.
    • Accepts: EventName.
    • Optional.

Examples

import { Emitter } from 'eventti';

const emitter = new Emitter();

emitter.on('a', () => {});
emitter.on('b', () => {});
emitter.on('b', () => {});
emitter.on('c', () => {});
emitter.on('c', () => {});
emitter.on('c', () => {});

emitter.listenerCount('a'); // 1
emitter.listenerCount('b'); // 2
emitter.listenerCount('c'); // 3
emitter.listenerCount(); // 6

Types

Here's a list of all the types that you can import from eventti.

import {
  EventName,
  EventListener,
  EventListenerId,
  Events,
  EmitterDedupe,
  EmitterOptions,
} from 'eventti';

EventName

type EventName = string | number | symbol;

EventListener

type EventListener = (...data: any) => any;

Events

type Events = Record<string | number | symbol, EventListener>;

EventListenerId

type EventListenerId = null | string | number | symbol | bigint | Function | Object;

EmitterDedupe

type EmitterDedupe = 'add' | 'update' | 'ignore' | 'throw';

EmitterOptions

type EmitterOptions = {
  dedupe?: EmitterDedupe;
  getId?: (listener: EventListener) => EventListenerId;
};

License

Copyright © 2022-2024, Niklas Rämö ([email protected]). Licensed under the MIT license.