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

fleg

v0.0.3

Published

🎌 A simple but powerful feature flag handling solution in less than 1Kb (min+gz). Browser + NodeJS.

Downloads

19

Readme

Fleg (https://en.wiktionary.org/wiki/fleg)

🎌 A simple but powerful feature flag handling solution.

  • Control through Cookies.
  • Control through Query String.
  • Automatic value conversion.
  • Browser support.
  • NodeJS support.
  • 0 dependency.
  • Less than 1Kb (min+gz).

Installation

npm i fleg

Usage

Fleg is meant to be initialized ONLY ONCE!

During bootstrap stage (at the very beginning) of your application, import Fleg and define your initial flags.

import { Fleg } from 'fleg'

new Fleg({
    enableFoo: true,
    enableBar: false,
    stringFlag: 'string'
})

Further on at any other part of the application use the default import. It will be the Fleg instance you created previously.

import fleg from 'fleg'

fleg.enableFoo // true

API

Fleg is extending Map which means all Map APIs are available. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map

fleg.get('enableFoo')
fleg.set('enableFoo', false)
// ...

set(key: string|array|object, value: any, writeCookie?: boolean)

Fleg overrides the default set method of Map to extend its functionality.

// Passing true will write this flag to cookies
fleg.set('key', 'value', true)

// You may pass an "entries shaped" array
fleg.set([
    ['key', 'value'],
    ['foo', 'bar']
])

// Pass object
fleg.set({
    enableFoo: 1,
    enableBar: 2
})

delete(key: string)

Delete a flag. It'll also remove associated cookies.

fleg.delete('enableFoo')

reset()

Reset flags back to initial state (what was passed to the constructor).

resetFleg Query String option

For convenience, you can add resetFleg query string to your URL to remove all cookie flags.

e.g. yourdomain.com?resetFleg

Globals

For convenience, the created Fleg instance can be accessed on the global scope both in NodeJS and the Browser.

global.__fleg
window.__fleg

Layered control

Fleg has 3 layers in the following order of loading:

  1. Initial flags: what is passed to the constructor.
  2. Cookie flags: cookie flags will override initial flags.
  3. Query String flags: will override all other flags AND will also set it as cookie, so it'll remain on next reload.

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.

License

MIT