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

@redpennon/node-sdk

v1.0.0

Published

RedPennon feature flag evaluation API client for Node.js

Readme

@redpennon/node-sdk

npm License: MIT

Thin HTTP client for the RedPennon feature flag evaluation API.

Installation

npm install @redpennon/node-sdk

Requires Node 20+. No runtime dependencies — uses the global fetch.

Quick start

import { RedPennonClient } from "@redpennon/node-sdk";

const client = new RedPennonClient({ apiKey: "YOUR_ENV_API_KEY" });

// Simple: get the resolved value or your default on any failure.
const enabled = await client.variableValue("dark-mode-enabled", {
  default: false,
});

// With user context (for targeting rules).
const user = { id: "user_123", email: "[email protected]" };
const enabled = await client.variableValue("dark-mode-enabled", {
  default: false,
  user,
});

// Full result: value + variation + reason.
const result = await client.variable("dark-mode-enabled", { user });
console.log(result.value, result.variation, result.reason);

// Batch: resolve many flags in one round-trip.
const results = await client.variables(["flag-a", "flag-b"], { user });
const flagA = results["flag-a"].value;

API

new RedPennonClient({ apiKey, baseUrl?, fetchImpl? })

| Option | Type | Description | |--------|------|-------------| | apiKey | string | Environment API key from the RedPennon dashboard. | | baseUrl | string? | Override the API base URL (default: https://api.redpennon.dev). | | fetchImpl | typeof fetch? | Custom fetch — useful for testing. |

client.variableValue(key, { default, user? }) → Promise<T>

Returns the resolved value or default on any failure (network error, non-2xx, value=null). Use this in production code — your default is the load-bearing contract.

client.variable(key, { user? }) → Promise<VariableResult>

Returns the full evaluation result (value, variation, reason, feature). Throws APIError on network or non-2xx errors.

client.variables(keys, { user? }) → Promise<Record<string, VariableResult>>

Batch evaluation — one HTTP round-trip for multiple flags. Unknown keys return reason: "variable_not_found" inline rather than throwing.

Local development

npm ci
npm test
npm run build

License

MIT © RedPennon