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

@plinthjs/cache

v0.1.0

Published

Mason cache: store contract, in-memory store, atomic locks, remember (the Illuminate\Cache equivalent).

Readme

@plinthjs/cache

The Mason cache layer — the Illuminate\Cache equivalent. A swappable store contract, an in-memory store, the user-facing repository (with remember), and atomic locks.

Everything that observes time takes an injected now clock (epoch milliseconds), so expiry and lock timeouts are deterministic. The default reads the system clock.

Usage

import { arrayCache } from '@plinthjs/cache'

const cache = arrayCache()

await cache.put('answer', 42, 60) // store for 60 seconds
await cache.get('answer') // 42
await cache.has('answer') // true

// Compute-once-then-cache. The callback runs only on a miss (and again after expiry).
const user = await cache.remember('user:1', 300, async () => fetchUser(1))
const config = await cache.rememberForever('config', loadConfig)

// Fetch-and-remove.
const flash = await cache.pull('flash')

// Atomic counters.
await cache.increment('hits') // 1
await cache.decrement('hits') // 0

Building blocks

import { ArrayStore, Repository } from '@plinthjs/cache'

const store = new ArrayStore() // implements the Store contract
const cache = new Repository(store)

Locks

const lock = cache.lock('reports', 10) // auto-expire after 10s

// Run a critical section only if the lock is free; always released afterwards.
const result = await lock.get(async () => generateReport())
if (result === false) {
  // someone else holds the lock
}

// Block until the lock is free, or throw LockTimeoutError after 5 seconds.
await lock.block(5, async () => generateReport())

Deterministic tests

Inject a fake clock so expiry never depends on the wall clock:

let now = 0
const cache = arrayCache({ now: () => now })

await cache.put('k', 1, 60) // expires at now + 60_000 ms
now = 60_001
await cache.get('k') // null — expired