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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@compie-technologies/node-leader

v0.1.7

Published

Leader Election Using Redis in Node.js.

Readme

node-leader

Leader Election Using Redis in Node.js.

Importing

// Using Node.js `require()`
const Leader = require('@compie-technologies/node-leader');

Installation

$ npm install @compie-technologies/node-leader

:warning: Important! node-leader requires JavaScript ES6 

Overview

In distributed computing, leader election is the process of designating a single process as the organizer of some task distributed among several computers (nodes).
Before the task is begun, all network nodes are either unaware which node will serve as the "leader" of the task, or unable to communicate with the current coordinator.
After a leader election algorithm has been run, however, each node throughout the network recognizes a particular, unique node as the task leader.
node-leader is a Nodejs implementation of the leader election algorithm backed by Redis.

const Leader = require('@compie-technologies/node-leader');
/**@type {RedisClient}*/
const client = require('redis').createClient();

// create new leader
/**@type {Leader}*/
const leader = new Leader(client);
console.log('id: ' + leader.id);
console.log('lock key: ' + leader.key);

The Leader constructor takes a second optional argument called 'options':

  • options.key - Redis key (default value is default)
  • options.ttl - Lock time to live in ms (will be automatically released after that time) (default value is 10000)
  • options.wait - Time between 2 tries getting elected in ms (default value is 1000)
const options = {
    key: 'some_key',
    ttl: 20000,
    wait: 2000
};

/**@type {Leader}*/
const leader = new Leader(client, options);

Actions

Before performing some task the candidate should try to get elected as the leader:

/**@type {Leader}*/
const candidate1 = new Leader(client, options);

console.log('candidate1 try to get elected as leader...');
leader1.elect();

Once elected, an ELECTED event will be triggered:

candidate1.on(Leader.event.ELECTED, async () => {
    console.log('candidate1 got elected!');

    try {
        let isLeader = await candidate1.isLeader();
        console.log(`candidate1 is ${isLeader ? '' : 'not '}the Leader!`);

    } catch (err) {
        console.error('err');
    }

    // performing some task
});

When finish the task, the candidate can stop being the leader:

console.log('candidate1 stop trying to be a leader...');
candidate1.stop();

Once revoked, a REVOKED event will be triggered:

candidate1.on(Leader.event.REVOKED, () => {
    console.log('candidate1 got revoked!');
});

Events

  • ELECTED when the candidate become leader.

  • REVOKED when the leader got revoked from his leadership.

  • ERROR when an error occurred.