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

@azasypkin/event-dispatcher

v1.0.0

Published

Simple ES6 pure Javascript event dispatcher.

Downloads

10

Readme

Event Dispatcher

Build Status codecov.io License

This file provides a helper to add custom events to any object.

Usage

In order to use this functionality with any object consumer should pick one of the following approaches: plain old mixin or ES6 Class extendsapproach:

class Obj extends EventDispatcher {}
const obj = new Obj();

Or mixin approach:

const obj = EventDispatcher.mixin({});

A list of events can be optionally provided and it is recommended to do so. If a list is provided then only the events present in the list will be allowed. Using other unknown events will cause other functions to throw an error:

class Obj extends EventDispatcher {
  constructor() { 
    super(['somethinghappened', 'somethingelsehappened']); 
  }
}
const obj = new Obj();

Or mixin approach:

const obj = EventDispatcher.mixin({ ... }, ['somethinghappened', 'somethingelsehappened']);

The object will have five new methods: on, once, off, offAll and emit. Use on to register a new event-handler:

obj.on("somethinghappened", function onSomethingHappened() { ... });

If the same event-handler is added multiple times then only one will be registered, e.g.:

function onSomethingHappened() { ... }
obj.on("somethinghappened", onSomethingHappened);
obj.on("somethinghappened", onSomethingHappened); // Does nothing

Use off to remove a registered listener:

obj.off("somethinghappened", onSomethingHappened);

Use once to register a one-time event-handler: it will be automatically unregistered after being called.

obj.once("somethinghappened", function onSomethingHappened() { ... });

And use offAll to remove all registered event listeners for the specified event:

obj.offAll("somethinghappened");

When used without parameters offAll removes all registered event handlers, this can be useful when writing unit-tests.

Finally use 'emit' to send an event to the registered handlers:

obj.emit("somethinghappened");

An optional parameter can be passed to 'emit' to be passed to the registered handlers:

obj.emit("somethinghappened", 123);