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

xev

v3.0.2

Published

Global event emitter

Downloads

14,955

Readme

xev

Global event system for Node. It works well on the cluster! (Messaging between master and workers)

Install

$ npm install xev --save

Usage

It is the same as using EventEmitter. But all events are shared globally.

Simple usage

File A:

import Xev from 'xev';

const ev = new Xev();

ev.on('my-event', message => {
	console.log(`message received: ${message}`);
});

File B:

import Xev from 'xev';

const ev = new Xev();

ev.emit('my-event', 'yo'); // <= 'message received: yo'

On the cluster

If you use the cluster, You must be call mount function at the master process. e.g.:

import { isMaster } from 'cluster';
import Xev from 'xev';

const ev = new Xev();

if (isMaster) {
	// your master code

	ev.mount(); // Init xev
} else {
	// your worker code
}

Worker A:

import Xev from 'xev';

const ev = new Xev();

ev.on('my-event', message => {
	console.log(`message received: ${message}`);
});

Worker B:

import Xev from 'xev';

const ev = new Xev();

ev.emit('my-event', 'yo'); // <= 'message received: yo'

Technically, Node.js cannot workers to communicate directly with each other - all communication goes via the master. So, you must be call our mount initialize function.

That is it.

Good luck, have fun.

API

Please see EventEmitter. In the following, we will describe the unique API of xev.

new Xev(namespace?)

If you are a library developer, we recommend setting namespace to avoid conflicts with events of users or other libraries:

import Xev from 'xev';

const ev = new Xev('my-namespace');

xev.mount()

If you want to share events on the cluster, please call this method once in the master process.

License

MIT