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

typed-feature-flagging

v1.1.3

Published

[![NPM Version](https://img.shields.io/npm/v/typed-feature-flagging)](https://www.npmjs.com/package/typed-feature-flagging)

Readme

typed-feature-flagging

NPM Version

Goals

  • able to substitute drivers
    • ie Unleash, LaunchDarkly, etc.
  • boolean feature flag (true/false) results
    • upstream driver failures will result in false (disabled)
  • exhaustive list of feature flags are defined ahead of time and typed (enums)
  • each feature flag may have a context type
    • if there was a context for the feature flag it MUST BE provided
    • the context is typed on a per feature flag basis (the user of the library must define the mapping of the feature flag name to the type of its value)

Desired API

Without a Context

enabled(FeatureFlag.WITHOUT_CONTEXT): boolean

If the developer had attempted to provide a context, there should have been a TS lint error indicating that the context value was not needed.

With a Context

enabled(FeatureFlag.WITH_CONTEXT, { ... }): boolean

If the developer had attempted to NOT provide a context, there should have been a TS lint error indicating that the context value was mandatory.