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

@clearlaunch/flags

v0.1.2

Published

ClearLaunch feature flags — guard features and routes behind flags you control from ClearLaunch.

Readme

@clearlaunch/flags

Feature flags for the browser, controlled from ClearLaunch. No dependencies.

npm install @clearlaunch/flags
import { clearFlags } from '@clearlaunch/flags';

const flags = clearFlags({
  projectKey: 'your-flag-project-key',   // ClearLaunch -> project -> Feature Flags
  environment: 'production',
  fallbacks: { 'new-checkout': false },  // used before load, and if we're unreachable
});

await flags.load({ id: user.id, plan: user.plan });

if (flags.isOn('new-checkout')) showNewCheckout();
const limit = flags.get('max-items', 10);

Failure is a first-class case

load() never throws and never leaves a read undefined. Reads fall back to the caller's argument, then fallbacks, then false. A flag service that can take down the app it gates is worse than no flag service.

ready tells you whether you have live values or fallbacks. A failed refresh keeps the last known-good values rather than reverting a running app.

API

| | | |---|---| | load(user?) | Fetch values. Call once at startup. | | identify(user) | Re-evaluate as a different user. | | refresh() | Re-fetch for the current user. | | isOn(key, fallback?) | Boolean read. | | get(key, fallback) | Typed read for string/number flags. | | detail(key) | Value plus reason and ruleId. | | all() | Every current value. | | subscribe(fn) | Called on every change. Returns an unsubscribe. | | ready | true once a load has succeeded. | | configVersion | Changes only when the flag config changes. |

Pass a stable id

Rollout percentage buckets on user.id, so the same user stays on the same side of a 20% rollout. Without it, a user can flip between page loads.

Values, not rules

This SDK receives evaluated values only — never your targeting rules. Rules name specific customers and unreleased work, and anything shipped to a browser is public. Use the server-side SDK when you need local evaluation with rules.

Auto-discovery

Keys you read are reported to ClearLaunch, so a flag used in code but never configured shows up as a draft rather than existing only in the source. A draft is never evaluated — it is there for you to see and decide on. Disable with reportKnownKeys: false.