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

swash-flag-sdk

v1.0.0

Published

A JavaScript SDK for Swash Feature Flags

Readme

Swash Feature Flags SDK

🚀 Introduction

Welcome to the Swash Feature Flags SDK! 🎉

This lightweight JavaScript SDK allows you to easily integrate feature flags into your application. Whether you're rolling out new features gradually or enabling experimental functionality, Swash Feature Flags has you covered. ✅

Unlike traditional authentication-based systems, the Swash Feature Flags SDK uses API tokens for authentication. This means you don’t have to deal with JWTs manually—just grab your API token from the Swash Flag Dashboard and start using feature flags immediately! 🔐


📦 Installation

First, install the SDK using your favorite package manager:

pnpm add swash-feature-flags-sdk
# or
npm install swash-feature-flags-sdk
# or
yarn add swash-feature-flags-sdk

🔧 Basic Implementation (Works Out of the Box)

Here’s a quick setup that fetches feature flags and evaluates them for a user:

import SwashFeatureFlags from "swash-feature-flags-sdk";

const featureFlags = new SwashFeatureFlags("https://api.swashflag.com", "YOUR_API_TOKEN");

// Fetch feature flags
featureFlags.fetchFlags().then(flags => {
  console.log("Feature Flags:", flags);
});

// Evaluate a flag for a user
featureFlags.evaluateFlag("new-dashboard", { id: "user-123" }).then(isEnabled => {
  console.log(isEnabled ? "✅ Feature is enabled!" : "❌ Feature is disabled.");
});

Where do I get an API token? 🤔

  • Go to the Swash Flag Dashboard.
  • Navigate to the API Tokens section.
  • Click "Generate API Token".
  • Copy the generated token and use it in the SDK.

🚦 Fetching All Feature Flags

Retrieve all available feature flags like this:

featureFlags.fetchFlags().then(flags => {
  console.log("Feature Flags:", flags);
});

This returns an array of feature flags:

[
  {
    "id": "dark-mode",
    "name": "Dark Mode",
    "enabled": false
  },
  {
    "id": "new-dashboard",
    "name": "New Dashboard UI",
    "enabled": true
  }
]

🎯 Evaluating a Feature Flag for a User

If you want to check whether a specific user has access to a feature, use:

featureFlags.evaluateFlag("new-dashboard", { id: "user-123", location: "US" }).then(isEnabled => {
  if (isEnabled) {
    console.log("✅ Feature is enabled!");
  } else {
    console.log("❌ Feature is disabled.");
  }
});

This will return true or false depending on the flag’s targeting rules.


🚀 Caching for Performance

The SDK automatically caches feature flags after fetching them to avoid unnecessary API requests. If you want to manually refresh the cache:

featureFlags.refreshFlags().then(flags => {
  console.log("🔄 Flags refreshed:", flags);
});

How does caching work?

  • The SDK stores feature flags in memory for 60 seconds (default).
  • If a request is made before the cache expires, it returns cached flags instead of hitting the API.
  • The cache resets on page reload, ensuring fresh data on new sessions.
  • Developers can manually refresh flags anytime using refreshFlags().

🛠 Advanced Configuration

You can customize caching behavior and logging options:

const featureFlags = new SwashFeatureFlags("https://api.swashflag.com", "YOUR_API_TOKEN", 30000); // Cache for 30 seconds

Available Options:

| Option | Description | Default | |-------------|---------------------------------|----------| | cacheTime | Time (in milliseconds) before cache expires | 60000 (60s) |


❓ Need Help?

If you have any questions or run into issues, feel free to open an issue or reach out to us! 🚀

Happy coding! 🎉