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/pennant

v0.1.0

Published

Mason feature flags (the Laravel Pennant equivalent).

Readme

@plinthjs/pennant

Mason feature flags — the Laravel Pennant equivalent.

Define a feature whose value depends on an optional scope (a user, a team, a request — anything). Resolved values are cached per (feature, scope), so each resolver runs once per scope.

import { FeatureManager } from '@plinthjs/pennant'

const feature = new FeatureManager()

// A simple on/off flag, resolved per scope.
feature.define('new-api', (user) => (user as { id: number }).id % 2 === 0)

// A richer "variant" value — `value()` surfaces it, `active()` coerces to truthiness.
feature.define('checkout-button', () => 'green')

const alice = { id: 2 }
await feature.active('new-api', alice) // => true
await feature.inactive('new-api', { id: 1 }) // => true
await feature.value('checkout-button', alice) // => 'green'

// Force a value regardless of the resolver.
feature.activate('new-api', { id: 1 }) // forced on
feature.deactivate('new-api', alice) // forced off
feature.forget('new-api', alice) // drop the cached/forced value — next read re-runs the resolver
feature.flushCache() // drop every cached value

// Bundle checks across features.
await feature.allAreActive(['new-api', 'checkout-button'], alice)
await feature.someAreActive(['new-api', 'checkout-button'], alice)

// A scope-bound accessor so you stop repeating the scope.
const forAlice = feature.for(alice)
await forAlice.active('new-api')
await forAlice.value('checkout-button')

Scope serialization

The cache key for a scope is computed by a serializer. The default handles:

  • undefined/null — the shared global/null scope.
  • primitives (string/number/boolean/bigint) — keyed by type:value.
  • objects exposing featureScopeId or id — keyed by that identifier.
  • anything else — keyed by JSON.stringify.

Pass your own via new FeatureManager({ serializer }).

Determinism

Pennant never reads the wall clock; caching is keyed purely on the serialized scope. Resolvers may be sync or async — active/value/etc. always return a Promise.