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

redis-events

v0.0.2

Published

Event emitter using redis as a data store

Downloads

23

Readme

Redis Events

Inter-process/inter-system event emitter

Redis event emitter is built against the node.js Event Emitter API. It helps scale out code built using event emitters without having to change any app related code (well, a signle line of code!). Simply require redis-events instead of events.

It supports all the methods exposed by Node's built-in event emitters.

Usage

Example

var EventEmitter = require('redis-events').EventEmitter;

// the following code stays exactly the same
var emitter = new EventEmitter();

emitter.on('msg', function(arg1, arg2, arg3) {});

emitter.emit('msg', 1, 2, 3);

Options

An options object can be passed to the event emitter to provide Redis connection options. Supported options include port, host and auth. These are passed straight to the node-redis module.

Example

var emitter = new EventEmitter({
	port: 12000,
	host: 'db-server.company.local'
});

Global defaults

To further assist the transition from using built-in event emitters to redis event emitters, the redis database options can be set globally once by editing the global defaults hash. Be careful when using this as it will apply these defaults application wide.

Example
// emitter-defaults.js

var EventEmitter = require('redis-events').EventEmitter;

// change global defaults
	// make sure this file is require'd before any other file that relies on event emitters
EventEmitter.defaults = {
	port: 12000,
	host: 'db-server.company.local'
};
// app.js

// nothing changes in this file except for the required module

var EventEmitter = require('redis-events').EventEmitter;

var emitter = new EventEmitter();

Gotchas

The data structure of arguments passed needs to be supported by both JSON.stringify and Redis. So, be careful if using objects such as Errors, Functions or arguments as event args.

Changelog

v0.0.2

  • Fix for issue #2
  • Added tests

v0.0.1

  • Initial commit