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

@nestjs-redisx/leader

v1.14.0

Published

Leader election plugin for NestJS RedisX — run cron jobs, migrations, and cleanup on exactly one instance, with heartbeat leases and automatic failover

Readme

@nestjs-redisx/leader

Leader election plugin for NestJS RedisX — run cron jobs, migrations, and cleanup on exactly one instance of your fleet, with lease heartbeats and automatic failover.

Why

Every multi-instance NestJS deployment hits the same problem: @Cron fires on every replica. Emails go out twice, cleanup jobs race, migrations collide. This plugin elects one leader per group over a Redis lease and gives you a one-line decorator to gate singleton work.

  • @LeaderOnly() — proxy-based method decorator for regular methods (generators are rejected at class load); composes with @nestjs/schedule (@Cron fires everywhere, the body runs only on the leader)
  • Lease-based election — atomic acquire (own-lease re-claim first, else SET NX PX), CAS Lua heartbeat, CAS release; single-key, cluster-safe
  • Automatic failover — instant on graceful shutdown (lease released), bounded by ttlMs + retryIntervalMs on crash
  • Fail-safe local view — isLeader() is true only while the last confirmed lease is unexpired; an unconfirmed renewal demotes immediately, and the still-held key is re-claimed on the next retry tick
  • Multiple independent groups — @LeaderOnly({ group: 'reports' }) registers its election automatically
  • Observability — onElected / onLost callbacks and redisx_leader_* counters with the Metrics plugin

Installation

npm install @nestjs-redisx/core @nestjs-redisx/leader ioredis
# or: npm install @nestjs-redisx/core @nestjs-redisx/leader redis

Quick start

import { Module, Injectable } from '@nestjs/common';
import { Cron, CronExpression } from '@nestjs/schedule';
import { RedisModule } from '@nestjs-redisx/core';
import { LeaderPlugin, LeaderOnly } from '@nestjs-redisx/leader';

@Module({
  imports: [
    RedisModule.forRoot({
      clients: { host: 'localhost', port: 6379 },
      plugins: [new LeaderPlugin()],
    }),
  ],
})
export class AppModule {}

@Injectable()
export class ReportJobs {
  @Cron(CronExpression.EVERY_HOUR)
  @LeaderOnly()
  async hourlyReport() {
    // Runs on exactly one instance of the fleet
  }
}

Programmatic API via LEADER_SERVICE (ILeaderService): isLeader(), getLeaderId(), runIfLeader(fn), stepDown(), getGroups(), instanceId.

Semantics to know

Leadership is a lease, not a fence: assume NTP-synced clocks and bounded event-loop pauses. For hard mutual exclusion inside leader work, combine with @nestjs-redisx/locks.

Documentation

Full reference: https://nestjs-redisx.dev/en/reference/leader/

License

MIT