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

audienceforge-js

v0.1.0

Published

Official JavaScript/TypeScript SDK for AudienceForge — feature flags and A/B testing.

Readme

audienceforge-js

Official JavaScript/TypeScript SDK for AudienceForge — feature flags and A/B testing.

  • Zero production dependencies (uses native fetch).
  • In-memory cache with configurable TTL.
  • Silent fallback: API errors never throw to your code — you always get a safe default.
  • Works in modern browsers and Node.js 18+. Ships ESM + CJS + type definitions.

Install

pnpm add audienceforge-js
# or: npm i audienceforge-js / yarn add audienceforge-js

Quick start

import { AudienceForge } from 'audienceforge-js';

const client = AudienceForge.init({ apiKey: 'sdk-key-xxxxx' });

if (await client.isEnabled('checkout-v2', { userId: 'u123', attributes: { plan: 'pro' } })) {
  // feature on
}

API

AudienceForge.init(config)

| Option | Type | Default | Description | |---------------|-----------------------|----------------------------------|----------------------------------------------| | apiKey | string (required) | — | SDK Key da organização (Bearer). | | apiUrl | string | https://api.audienceforge.dev | URL base da API. | | environment | string | production | Ambiente avaliado. | | cacheTtlMs | number | 30000 | TTL do cache local (0 desabilita). | | timeoutMs | number | 1000 | Timeout por request antes do fallback. | | fetchImpl | typeof fetch | globalThis.fetch | Implementação de fetch (Node < 18 / testes). |

client.isEnabled(flagKey, userContext): Promise<boolean>

Avalia se a flag está habilitada. Fallback: false.

client.getVariant(flagKey, userContext): Promise<string>

Retorna a variante ativa da flag. Fallback: 'control'.

client.evaluateExperiment(experimentKey, userContext): Promise<{ variant: string }>

Atribui a variante de um experimento A/B. Fallback: { variant: 'control' }.

Nota de backend (jun/2026): o método evaluateExperiment depende da implementação determinística de avaliação no experiments-service (DT-06). Até esse fix estar em produção, o backend pode retornar sempre control.

UserContext: { userId: string; attributes?: Record<string, string | number | boolean> }.

Behavior

  • Cache: avaliações idênticas (mesma flag/experimento + userId + environment + atributos) dentro do TTL não geram nova chamada HTTP.
  • Fallback silencioso: timeout, erro de rede, 4xx/5xx ou JSON inválido resolvem com o valor padrão; nenhuma exceção é propagada.

Endpoints usados

  • Flags: POST {apiUrl}/flags/api/v1/evaluate
  • Experiments: POST {apiUrl}/experiments/api/v1/experiments/evaluate

Development

pnpm install
pnpm test        # vitest (sem rede — fetch mockado)
pnpm run build   # tsup → dist (ESM + CJS + d.ts)
pnpm run typecheck

License

MIT