New:Microsoft Teams Notifications Are Now Available in Socket.Learn more →
Get Started

@featureflip/browser

Package Overview
Dependencies
Maintainers
1
Versions
19
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@featureflip/browser

Browser SDK for Featureflip - framework-agnostic feature flag client

latest
Source
npmnpm
Version
2.10.0
Version published
Weekly downloads
59
-72.17%
Maintainers
1
Weekly downloads
 
Created
Source

@featureflip/browser

Framework-agnostic browser SDK for evaluating Featureflip feature flags.

Installation

npm install @featureflip/browser

Quick Start

import { FeatureflipClient } from '@featureflip/browser';

const client = FeatureflipClient.get({
  clientKey: 'your-client-sdk-key',
});

await client.initialize();

const showBanner = client.boolVariation('show-banner', false);

Singleton by construction. FeatureflipClient.get() is the only way to obtain a client — the public constructor was removed in v2.0. Calling get() more than once with the same clientKey returns handles pointing at one shared underlying client (refcounted). This makes framework bindings, React StrictMode double-mounts, and per-component construction all harmless — they all resolve to one SSE connection and one flag store per key.

API Reference

FeatureflipClient.get(config)

FeatureflipClient.get(config: FeatureflipClientConfig): FeatureflipClient

Returns a client for the given client key. The first call constructs and registers a shared core; subsequent calls with the same key return a new handle pointing at the cached core. When the last handle for a key is closed, the core shuts down and is removed from the cache.

Configuration Options

OptionTypeDefaultDescription
clientKeystring(required)Client SDK key from your project settings
baseUrlstringhttps://eval.featureflip.ioEvaluation API base URL
contextRecord<string, unknown>{}Initial evaluation context (user attributes)
streamingbooleantrueEnable SSE streaming for real-time updates
initTimeoutnumber10000Timeout in ms for the initial evaluate request

Methods

initialize(): Promise<void>

Fetches all flag values from the server. Must be called before reading variations. Opens an SSE streaming connection if streaming is enabled.

boolVariation(key: string, defaultValue: boolean): boolean

Returns a boolean flag value, or defaultValue if the flag is missing or not a boolean.

stringVariation(key: string, defaultValue: string): string

Returns a string flag value, or defaultValue if the flag is missing or not a string.

numberVariation(key: string, defaultValue: number): number

Returns a number flag value, or defaultValue if the flag is missing or not a number.

jsonVariation<T>(key: string, defaultValue: T): T

Returns a flag value cast to T, or defaultValue if the flag is missing.

identify(context: Record<string, unknown>): Promise<void>

Re-evaluates all flags with a new context (e.g., after login). Emits change events for any flags whose values changed.

await client.identify({ user_id: '123', plan: 'pro' });

on(event: EventType, handler: EventHandler): void

Subscribe to events.

  • 'ready' -- fired after initialize() completes
  • 'change' -- fired when flag values change (receives a FlagChanges object)
  • 'error' -- fired on streaming or network errors
client.on('change', (changes) => {
  console.log('Flags changed:', changes);
});

off(event: EventType, handler: EventHandler): void

Unsubscribe from events.

close(): void

Decrements the refcount on the shared core. When the last handle for a given client key is closed, the shared core closes the SSE connection and removes itself from the factory cache. Double-close on the same handle is a no-op.

Testing

Use FeatureflipClient.forTesting() to create a client with predetermined flag values -- no network calls.

const client = FeatureflipClient.forTesting({
  'show-banner': true,
  'button-color': 'blue',
});

client.boolVariation('show-banner', false); // true
client.stringVariation('button-color', 'red'); // 'blue'

License

Apache-2.0

FAQs

Package last updated on 18 Sep 2026

Related posts