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-manager

v1.0.0

Published

Feature flag manager for SaaS and white-label products

Downloads

32

Readme

medicast-app-framework

Feature flag manager for SaaS and white-label products

Test status Circle CI

Overview

Use feature-manager when you have an externalized configuration that you need to load to enable and disable features. For now it's just a small abstraction layer to pull in a catalog file from a local or remote source--not that interesting. But we'll be adding some smart stuff soon like auto-reloading at a configurable interval + a back-end service and UI to manage features, etc.

Usage

Basic Flow

var FeatureManager = require('feature-manager');

var options = { /* see below */ };
var featureManager = new FeatureManager(options);

// blocking call
featureManager.isEnabledSync('mainpage.sidebar');		// returns true, false

// using promises
featureManager.isEnabled('mainpage.sidebar').then(function(enabled) {
	// enabled is true or false
});

Initializing

var options = {
	sourceType: FeatureManager.SourceType.Local,		// or just 'local'
	sourcePath: __dirname + '/features.json',
	ttl: 86400	
	// see below for additional configurations
};
var featureManager = new FeatureManager(options);

Options is an object containing details on where and how often to retrieve the feature catalog. Currently, feature catalog files can be stored locally or on AWS S3:

var options = {
	sourceType: FeatureManager.SourceType.S3,		// or just 's3'
	sourceBucket: 's3.bucket.example.com',
	sourcePath: 'path/to/features.json',
	ttl: 86400,
	aws: {
		accessKeyId: 'AMAZON-ACCESS-KEY-ID',
		secretAccessKey: 'SECRETACCESSKEY'
	}
}

Feature Catalog Format

The catalog is a JSON file that contains an object whose keys represent features that you wish to enable or disable. Values can be either true/false to indicate that the feature is enabled, or an object that contains additional configuration elements for the feature.

{
	"feature1" : true,
	"feature2" : { 
		"optionA" : "some value",
		"optionB" : "another config element"
	},
	"feature3" : {
		"enabled" : false,
		"optionA" : "red"					// unused
	},
	"feature4": {
		"enabled" : true,					// redundant
		"optionX" : "/path/to/something"
	}
}

Note the presence of the enabled key, which can be used to explicitly enable/disable a feature. Setting this to true is redundant because the presence of options for a feature key indicates that it is enabled, but it's provided as syntactic sugar and to help maintain consistency.

At this time, the catalog cannot include nested feature containers, i.e. the following is not valid syntax:

{
	"mainpage" : {
		"sidebar": false,
		"navbar" : {
			"enabled" : true,
			"theme" : "light"
		}
	}
}

This capability will be added in a later version. The workaround is to do this for now:

{
	"mainpage.sidebar" : false,
	"mainpage.navbar" : {
		"theme" : "light"
	}
}

License

MIT License. Our gift to you--happy birthday. Use at your own risk.