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

@zeruxjs/cache

v0.0.3

Published

cache on browser application

Readme

@zeruxjs/cache

Application cache abstraction with a built-in bounded memory cache, external adapters, and a manager facade. Cache values are JSON-serializable. Cache keys should not contain secrets.

Setup

import { createCacheManager, createMemoryCacheHelper, createCacheManagerWithHelper } from '@zeruxjs/cache';

const cache = await createCacheManager({
  helper: 'memory', // or '@zeruxjs/cache-redis' for Redis
  prefix: 'project:users', // keys are project:users:<name>
  defaultTtlSeconds: 300,
  options: { maxEntries: 2000 }
});

await cache.set('u:42', {name: 'Ada'}, {ttlSeconds: 30});
const users = await cache.getMany(['u:42', 'u:43']); // logical/unprefixed keys
await cache.clear(); // namespace only

createCacheManagerWithHelper(adapter, config) allows testing or injecting an existing adapter. createMemoryCacheHelper({maxEntries, now}) implements LRU eviction, lazy TTL expiry, defensive JSON cloning, numeric counters, conditional ifAbsent/ifPresent writes, bulk methods, and stats.

Cache stampede prevention

const item = await cache.remember('catalog', async () => fetchCatalog(), {ttlSeconds: 60});

Concurrent misses for the same key within one manager process share one pending producer Promise. Failed producers are not cached. It is not a distributed lock and cannot prevent concurrent work across Redis clients or server instances.

Safety notes

  • clear() with a prefix must call the provider's clearPrefix implementation; it fails closed if unsupported. Without a prefix it calls the provider's global clear, which Redis disables by default.
  • TTLs must be positive and finite; counters accept non-negative safe integers.
  • Values are JSON-serializable. The memory provider copies objects on get/set to avoid accidental mutation.
  • Memory cache is per process: no persistence, synchronization, or cross-worker coordination.
  • Conditional writes are atomic only when the provider supports them. setMany across multiple keys is not guaranteed atomic.

Run package tests after building: npm run build && node --test test/*.test.mjs.

Release 0.0.2

Prepared to validate npm trusted publishing through GitHub Actions.

Release 0.0.3

Synchronized ecosystem release, including Zuixs CSS-entry support and documentation updates. Existing placeholder packages retain their documented limitations.