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 🙏

© 2024 – Pkg Stats / Ryan Hefner

feature-helper

v1.0.1

Published

Wrapper library that helps widgets verify enabled features on the app from various sources.

Downloads

6

Readme

feature-helper

This library is a helper to abstract all different sources of feature flag services on your application. Regardless of any feature flag source, format, or type, it can help you connect to one API in order to work with feature flags in runtime.

The library is written in TypeScript and is compatible for use with JavaScript as well.

##Installation

yarn add @bills/feature-helper

or

npm i @bills/feature-helper --save

Usage

TypeScript syntax - You can import the interfaces as well

import { FeatureFlagHelper, IFeatureSource, TFetcher, TTransformer } from '@bills/feature-helper';

EcmaScript 2015 syntax

import { FeatureFlagHelper } from '@bills/feature-helper';

EcmaScript5 syntax

var FeatureHelper = require('@bills/feature-helper');
var FeatureFlagHelper = FeatureHelper.FeatureFlagHelper;

Pass your feature flag sources to the constructor method in an array. The Flag sources need to implement the IFeatureSource interface.

interface IFeatureSource<T> {
    sourceName: string;
    fetcher: TFetcher<T>;
    transformer?: TTransformer<T>;
}

fetcher - TFetcher<T>

type TFetcher<T> = () => Promise<T>;

The Fetcher Function is a function that can asynchronously retrieve all feature flag data. This may be a remote call, a database read, etc... What it is does not matter to the library. All that matters is that is returns a promise, and the type that gets resolved in the promise is of generic type T. Type T is important for the Transformer function, explained below.

transformer - TTransfomer<T>

type TTransformer<T> = (featureObj: T) => TFeatures;
type TFeatures = IFeature[];
interface IFeature {
    name: string;
    source: string;
    value: any;
}

The Transformer Function takes the result of the fetcher call (the type was generic T, remember?), and translates it into an array of IFeatures. IFeature is pretty simple: name of the feature flag, the source it came from, and the value. Most likely, the value will be a boolean, but some feature flags do have other types such as string, number, or object.

So...

Construct the class like the following

const featureSource = {
  name: 'Local Properties',
  fetcher: async () => { /*...*/ },
  transfrormer: (response: T) => { /*...*/ }
};

const FeatureFlags = new FeatureFlagHelper(featureSource);

NOTE: Validation

The IFeatureSource fields are extremely important and they will be validated at the constructor. If they are invalid, the constructor will throw an Error. You can check it by calling FeatureFlagHelper.isValidFeatureSource(mySource) and retrieve a boolean.

Usage cont'd...