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

konfigo-sdk

v0.1.1

Published

Official JavaScript/TypeScript SDK for Konfigo feature flags and remote config.

Readme

konfigo-sdk

Official JavaScript/TypeScript SDK for Konfigo — feature flags and remote config. Zero dependencies, works in Node 18+, Bun, Deno, edge runtimes and browsers (anything with fetch).

npm install konfigo-sdk

Usage

import { Konfigo } from "konfigo-sdk";

const konfigo = new Konfigo({
  apiKey: process.env.KONFIGO_API_KEY!, // kfg_... (bound to one project + environment)
  baseUrl: "https://your-konfigo-host",
});

await konfigo.start(); // initial load + refresh every 30s

if (konfigo.isEnabled("new-checkout")) { /* ... */ }
const timeout = konfigo.get("api_timeout_ms", 3000);

Without background polling: await konfigo.refresh() when you want, or call fetchFlags() / fetchConfig() for uncached reads.

API

| | | |---|---| | new Konfigo({ apiKey, baseUrl, timeoutMs?, fetch? }) | Create a client | | start({ intervalMs?, onError? }) / stop() | Load and poll in the background | | refresh() | Load flags + config into the cache | | isEnabled(key, fallback = false) | Flag state from cache | | get(key, fallback?) | Config value from cache (numbers stay numbers) | | onChange(fn) | Subscribe to refreshes; returns unsubscribe | | fetchFlags() / fetchConfig() | Uncached reads | | current | Last snapshot { env, flags, config } |

Failed background refreshes keep the last good values. Errors are KonfigoError with status and (on 429) retryAfter seconds. The API allows 120 requests/min per key; the default polling uses 4.

Keys created as "Flags only" can be used in client-side code; pass flagsOnly: true so the SDK skips the config endpoint. baseUrl must be https:// (plain http:// is only accepted for localhost), and responses are type-checked before they reach your cache.

Don't ship a server API key to the browser — it grants read access to all values in that environment.