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

@prsm/lock

v1.0.2

Published

Distributed locking primitives for Redis - mutex and semaphore

Readme

Distributed locking primitives for Redis. Mutex (exclusive lock) and semaphore (N concurrent leases). Atomic, safe, crash-tolerant.

Installation

npm install @prsm/lock

Mutex

Exclusive lock. One holder at a time.

import { mutex } from "@prsm/lock"

const lock = mutex({
  redis: { host: "127.0.0.1", port: 6379 },
})

const { acquired, id } = await lock.acquire("my-job", { ttl: "30s" })
if (!acquired) return

try {
  await doWork()
} finally {
  await lock.release("my-job", id)
}

mutex(options)

  • redis - { url?, host?, port?, password? } passed to node-redis
  • prefix - Redis key prefix (default "lock:mutex:")

Methods

| Method | Returns | Description | |---|---|---| | acquire(key, opts?) | { acquired, id } | Attempt to acquire. opts.ttl (default "10s"), opts.id (custom holder ID) | | release(key, id) | boolean | Release only if you still own it | | peek(key) | { held, holder, ttl } | Check lock state without acquiring | | close() | void | Disconnect Redis |

Semaphore

Up to N concurrent holders.

import { semaphore } from "@prsm/lock"

const sem = semaphore({
  max: 20,
  ttl: "60s",
  redis: { host: "127.0.0.1", port: 6379 },
})

const { acquired, id } = await sem.acquire("worker-slots")
if (!acquired) return

const heartbeat = setInterval(() => sem.renew("worker-slots", id), 15000)

try {
  await processTask()
} finally {
  clearInterval(heartbeat)
  await sem.release("worker-slots", id)
}

semaphore(options)

  • max - Maximum concurrent holders (required)
  • ttl - Lease lifetime (default "60s"). Expired leases are pruned automatically
  • redis - Same as mutex
  • prefix - Redis key prefix (default "lock:sem:")

Methods

| Method | Returns | Description | |---|---|---| | acquire(key, opts?) | { acquired, id } | Acquire a lease slot. opts.id for custom lease ID | | release(key, id) | true | Release a lease | | renew(key, id) | boolean | Extend lease lifetime. false if expired | | count(key) | number | Active lease count (after pruning) | | peek(key) | { active, max, available, holders } | Full semaphore state | | close() | void | Disconnect Redis |

How It Works

Mutex uses SET key value NX PX ttl for atomic acquire and a Lua script for ownership-checked release (only the holder can release).

Semaphore uses a Redis sorted set where each member is a lease ID and the score is a timestamp. Expired entries are pruned via ZREMRANGEBYSCORE before each acquire. Renewal updates the timestamp to extend the lease window.

Both are crash-tolerant via TTLs. If a holder dies without releasing, the lock/lease expires automatically.