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

hush-hush

v2.0.0

Published

Feature flagging for when you need to keep it hush-hush.

Downloads

9

Readme

hush-hush@v2

npm Dependencies

For when you need to keep that Super Secret Beta Feature "hush-hush".

hush-hush lets you enable features in your application when the state you provide matches a set of criteria.

Install

hush-hush is available as Node module. Bundle it for the browser with Browserify or Webpack.

:warning: v2 is a breaking change from the v1 alphas. The API has changed significantly.

$ npm install --save hush-hush

In your application, require or import it.

const HushHush = require('hush-hush');

Usage

new HushHush(criteria:Array)

First, create an new HushHush instance of a feature you might want to enable (with or without a set of criteria).

// Create an instance without any criteria.
const const secretBetaFeature = new HushHush();

// Create an instance with an array of the initial criteria.
const secretBetaFeature = new HushHush([
  { environment:'beta', role:'tester' },
  { environment:'^prod(uction)?$', user:'bbe6a53d-cee3-4562-af08-c892a4b3ca62' }
]);

// Create an instance with an initial criteria object.
const secretBetaFeature = new HushHush({ environment:'beta', role:'tester' });

criteria is a plain Object - for best results try not to nest properties. You'll notice that strings are converted to regular expressions.

.add(criteria:Array,Object)

You can add additional sets of criteria later. Just .add it with an Array or Object.

secretBetaFeature.add({ environment:'beta', role:'beta-opt-in' });

.remove(criteria:Object)

You can remove individual sets of criteria from a feature:

secretBetaFeature.remove({ environment:'beta', role:'tester' });

Or remove all criteria at once:

secretBetaFeature.remove();

.test(state:Object, callback:Function)

Once you've defined all of your features and the criteria needed for each to be enabled, you'll test against an object describing the current state.

let state = {
  environment: 'beta',
  role: 'tester',
  user: 'bbe6a53d-cee3-4562-af08-c892a4b3ca62'
};

secretBetaFeature.test(state, (err, { enabled, matches }) => {
  if (enabled) {
    console.log(`"Secret Beta Feature" is enabled because it matched ${matches.length} set(s) of criteria.`);
  }
});

The state provided will be matched against each set of criteria. If any of the sets of criteria match, the feature is enabled.

When the test is complete, callback is executed, unless it's omitted, in which case a Boolean is returned.

secretBetaFeature.test(state) // ==> true

License

(The MIT License)

Copyright (c) 2017 John Flesch.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.