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

@getflaggy/sdk

v0.3.1

Published

JavaScript/React SDK for the Flaggy feature flag server

Readme

@getflaggy/sdk

JavaScript/React SDK for the Flaggy feature flag server.

  • Zero runtime dependencies
  • Server-side evaluation with local cache
  • Real-time updates via SSE
  • React bindings with useFlag hook
  • TypeScript, dual ESM/CJS

Install

npm install @getflaggy/sdk

React

Setup

Wrap your app with FlaggyProvider:

import { FlaggyProvider } from '@getflaggy/sdk/react';

function App() {
  return (
    <FlaggyProvider
      serverUrl="https://flaggy.example.com"
      apiKey="your-api-key"
      flags={['show-banner', 'dark-mode']}
      context={{ userId: '123', plan: 'pro' }}
      onError={(err) => console.error(err)}
    >
      <MyApp />
    </FlaggyProvider>
  );
}

Read a flag

import { useFlag } from '@getflaggy/sdk/react';

function MyComponent() {
  const showBanner = useFlag('show-banner', false);

  if (!showBanner) return null;
  return <div>New feature!</div>;
}

useFlag(key, defaultValue) returns the server-evaluated value, or defaultValue if the flag doesn't exist or the provider isn't ready yet.

Access client state

import { useFlaggy } from '@getflaggy/sdk/react';

function Status() {
  const { ready, error } = useFlaggy();

  if (error) return <div>Error: {error.message}</div>;
  if (!ready) return <div>Loading...</div>;
  return <div>Flags loaded</div>;
}

Provider props

| Prop | Type | Default | Description | |------|------|---------|-------------| | serverUrl | string | — | Flaggy server URL | | apiKey | string | — | API key | | flags | string[] | — | List of flag keys to evaluate | | context | Record<string, unknown> | {} | Evaluation context (user info, etc.) | | enableStreaming | boolean | true | Enable SSE for real-time flag updates | | onError | (error: Error) => void | — | Error callback (Sentry, Datadog, etc.) |

When context changes (deep comparison), flags are automatically re-evaluated.

Vanilla JavaScript

import { FlaggyClient } from '@getflaggy/sdk';

const client = new FlaggyClient({
  serverUrl: 'https://flaggy.example.com',
  apiKey: 'your-api-key',
  flags: ['show-banner', 'dark-mode'],
  context: { userId: '123' },
});

client.on('ready', () => {
  console.log(client.getFlag('show-banner', false));
});

client.on('change', (key, value) => {
  console.log(`Flag ${key} changed to`, value);
});

client.on('error', (err) => {
  console.error(err);
});

await client.initialize();

// Update context (re-evaluates all flags)
await client.setContext({ userId: '456', plan: 'enterprise' });

// Cleanup
client.destroy();

How it works

  1. On init, the SDK calls POST /api/v1/evaluate/batch with the declared flag keys
  2. Results are cached locally — getFlag() reads from cache (synchronous)
  3. An SSE connection to /api/v1/stream listens for flag changes in real-time
  4. On change events, the affected flag is re-evaluated via POST /api/v1/evaluate
  5. SSE reconnects automatically with exponential backoff + jitter

License

MIT