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

@zoxon/eventor

v1.0.0

Published

An event handling utility that provides a simple API for creating custom events and registering listeners

Downloads

12

Readme

@zoxon/eventor

An event handling utility that provides a simple API for creating custom events and registering listeners

The eventor name is combination of "event" and "creator".

This library provides a simple API for creating custom events and registering listeners. It also includes helper methods for managing event listeners and triggering events with custom data. It uses TypeScript to ensure type safety when working with events.

Usage

To use this utility, you first need to import the functions you want to use:

import { listenEvent, unlistenEvent, dispatchCustomEvent } from '@zoxon/eventor';

You also need to register your custom event types in env.d.ts if you use a TypeScript, like so:

declare interface WindowEventMap {
  'modal:show': CustomEvent<string>
  'modal:close': CustomEvent<string>
}

Note: In this example type string is a type for data that can be emitted with your custom event.

Adding an Event Listener

To add an event listener for a custom event, use the listenEvent function. It takes two parameters: the name of the event to listen for, and a callback function that will be called when the event is triggered.

function handleModalShow(event: CustomEvent<string>) {
  console.log(`The modal with ID "${event.detail}" has been shown.`);
}

listenEvent('modal:show', handleModalShow);

The listenEvent function returns a function that you can use to remove the event listener:

const unlisten = listenEvent('modal:show', handleModalShow);

// Later, to remove the event listener:
unlisten();

Removing an Event Listener

To remove an event listener for a custom event, use the unlistenEvent function. It takes the same two parameters as listenEvent: the name of the event and the callback function.

function handleModalShow(event: CustomEvent<string>) {
  console.log(`The modal with ID "${event.detail}" has been shown.`);
}

listenEvent('modal:show', handleModalShow);

// Later, to remove the event listener:
unlistenEvent('modal:show', handleModalShow);

Dispatching a Custom Event

To dispatch a custom event, use the dispatchCustomEvent function. It takes two parameters: the name of the event to dispatch, and the data that should be attached to the event.

dispatchCustomEvent('modal:show', 'myModal');

In this example, a custom event with the name modal:show is dispatched, and the string 'myModal' is attached as the event detail.

The dispatchCustomEvent function will automatically infer the correct type for the event detail based on the event name, so you don't need to specify it manually.

dispatchCustomEvent('modal:close'); // No event detail is attached
dispatchCustomEvent('modal:open', 'my-modal-id'); // The string 'my-modal-id' is attached as the event detail