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

@configdirector/openfeature-server-provider

v1.12.0

Published

OpenFeature server provider for ConfigDirector. ConfigDirector is a remote configuration and feature flag service.

Readme

ConfigDirector OpenFeature Node.js Provider

npm

OpenFeature Node.js provider SDK for ConfigDirector, remote config and feature flags with typed values, JSON Schema validation, and safe renames of live flags. Start free, no card required.

Install

npm install --save @configdirector/openfeature-server-provider @openfeature/server-sdk

Retrieve a value

import { OpenFeature } from "@openfeature/server-sdk";
import { ConfigDirectorProvider } from "@configdirector/openfeature-server-provider";

// The server SDK key is a secret. Do not commit it to your source code.
await OpenFeature.setProviderAndWait(new ConfigDirectorProvider("YOUR-SERVER-SDK-KEY"));
const client = OpenFeature.getClient();

const newCheckout = await client.getBooleanValue("new-checkout", false);

setProviderAndWait rejects when no config arrives from ConfigDirector within the connection timeout, which is 3 seconds unless you set connection.timeout in milliseconds. Flags then resolve to their in-code default values until config arrives. To start without waiting for ConfigDirector, set the provider with setProvider instead:

OpenFeature.setProvider(new ConfigDirectorProvider("YOUR-SERVER-SDK-KEY"));

Or catch the rejection:

try {
  await OpenFeature.setProviderAndWait(new ConfigDirectorProvider("YOUR-SERVER-SDK-KEY"));
} catch (error) {
  console.warn("Starting on in-code default values until ConfigDirector sends config:", error);
}

Full details are in the official documentation.

Test your code

Tests of code that reads flags through OpenFeature swap the provider for the in-memory one the OpenFeature Node.js SDK ships, TypedInMemoryProvider (@openfeature/server-sdk 1.21 and newer), so the test controls the values and nothing from ConfigDirector is involved:

import { OpenFeature, TypedInMemoryProvider } from "@openfeature/server-sdk";

const provider = new TypedInMemoryProvider({
  "new-checkout": { variants: { on: true, off: false }, defaultVariant: "on" },
});
await OpenFeature.setProviderAndWait(provider);
const client = OpenFeature.getClient();

expect(await client.getBooleanValue("new-checkout", false)).toBe(true);

provider.putConfiguration({
  "new-checkout": { variants: { on: true, off: false }, defaultVariant: "off" },
});
expect(await client.getBooleanValue("new-checkout", true)).toBe(false);

Full details are in the testing section of the official documentation.

Documentation

Refer to the official documentation for the OpenFeature Node.js provider.

There is also a quickstart guide for ConfigDirector and any of our SDKs.

Getting Help