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

ragflag

v0.2.1

Published

Boolean flag manager with MongoDB (using Mongoose) persistence.

Downloads

2

Readme

RagFlag

Boolean flag manager with MongoDB (using Mongoose) persistence.

About

RagFlag let's you manage "flags". Flags are basically named collections of booleans tied to a specific identifier.

API

During application launch or similar you'll have to configure the available flags with RagFlag somehow. This is to make it easier to validate input and such, mainly so that you don't write a typo or something.

var connection = mongoose.createConnection();
var RagFlag = require('ragflag');
var ragflag = new RagFlag(connection);

// `user_state` in this case is a `namespace`, ie. a collection of flags.
// You can have how many you'd like and each collection can have any number of
// flags defined.
//
// In this example we are configuring flags that track our user's progress
// through an onboarding or similar. We might use this state to decide whether
// or not we want to show a tooltip or something.
ragflag.configure('user_state', [
  'has_seen_new_thing',
  'has_visited_special_page'
]);

Once you're all set up it's just a matter of reading and writing the flags. Each collection can be associated with any number of identifiers. In the example above we might have one such user_state collection per user id.

Continuing on the the above example, a request comes in and we need to render a page. Before we can render it we need to know whether or not we should include the template for a special dialog that tells a first time user what they are seeing.

ragflag.get('user_state', user.id, function (err, flags) {
  if (!flags.check('has_visited_special_page')) {
    renderHelpDialog();
    flags.set('has_visited_special_page', true);
  }
});

new RagFlag(connection, flags)

connection should be a mongoose connection object. flags is optional and should be an object with keys representing namespaces and values repsenting their valid flags. See configure() below.

RagFlag.configure(namespace, flags)

Configure a namespace with the given flags. flags should be an array of strings.

namespace can also be an object where the keys are the names of the namespaces and the values are an array of flags.

RagFlag.get(name, id, fn)

Fetches the flags for a given id in the given namespace. The Flags object will be passed to the fn as the second argument. First argument is any error that occured.


Flags is the object fetched by RagFlag.get().

Flags.set(flag, on, fn)

Sets the flag to the vaue on. flag must be a valid flag for the current namespace. on must be a boolean.

fn is optional and called once the update has been persisted in MongoDB. The change will be persisted even if you don't supply a callback.

Flags.check(flag)

Returns a boolean telling you whether or not flag is true for the current namespace.

Flags.refresh(fn)

If you think the flags might've been updated from elsewhere in your application you can use refresh to update the state of the current Flags object to match what's in your database.

Events

RagFlag

The following events are emitted by RagFlag:

  • saved, emitted whenever a Flag is saved. Passes a plain JavaScript object representation of the saved flag to the listeners.
  • error, emitted whenever an error saving a Flags object occurs.

Flags

The following events are emitted by Flag objects:

  • changed, whenever set is called on a particular Flags object.
  • refreshed, emitted when on a Flags object if it's refreshed.

License

Distributed under the MIT license.