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-grape

v1.3.1

Published

A tool that allow developers make their own event management.

Downloads

13

Readme

EventGrape

A library that allow developers to manage their own events.

Installation

$ npm install event-grape

Usage

import EventGrape from "event-grape";

// Define your own events for each namespace before creating a new event grape.
// You can not add or remove events from an existing instance.
const events = {
  namespaceA: ["eventA", "eventB"],
  namespaceB: ["eventA"],
};

// Create a new event grape.
const eventGrape = new EventGrape(events);

const remove = eventGrape.listen("namespaceA", "eventA", () => {
  console.log("Event namespaceA/eventA has been emitted.");
  // ...
});

// Dispatch event whenever you want.
eventGrape.dispatch("namespaceA", "eventA");
// Output: Event namespaceA/eventA has been emitted.

// Remove the event listener once you don't need it anymore.
remove();

Instance Methods

listen(namespace: string, event: string, callback: (payload?: any) => void)

Register a new listener that continuously listen to the event under that namespace. Return a function used to unregister this listener.

let remove = eventGrape.listen("namespaceA", "eventA", () => {
  // Do something amazing.
});

// Unregister this listener once you don't need it.
remove();

once(namespace: string, event: string, callback: (payload?: any) => void)

Basically same as "listen" with only one difference, it will be unregistered immediately after being invoked. Return a function used to unregister this listener.

let remove = eventGrape.once("namespaceA", "eventA", () => {
  // This listener will be invoked only one time.
});

// You still can unregister it before invoked.
remove();

dispatch(namespace: string, event: string, payload?: any)

Dispatch the event under that namespace and invoke all listeners. The payload will pass to listeners if it has been assigned.

let payload = "foo";
eventGrape.dispatch("namespaceA", "eventA", payload);

clear(namespace: string, event: string)

Unregister all listeners of the event under that namespace.

eventGrape.clear("namespaceA", "eventA");

License

MIT