JavaScript Feature Flags

JavaScript Feature Flag Resources/Solutions

  • LaunchDarkly JavaScript Feature Flag SDK – LaunchDarkly
    • An installable feature flag software development kit for JavaScript and single page apps (Ember/Angular/React).  This SDK harnesses the LaunchDarkly app and allows you to target users and manage rollouts.  Feature flags are evaluated in microseconds.
    • Main Website
    • Front-end Flags
    • GitHub Repo
  • JavaScript Feature Flags – Jay Fienberg
    • “This Javascript function gets Feature Flags set in the URL (as fragment and/or query string), set in a browser cookie, and/or via matching a domain name (e.g., localhost, or your test domain name).”
    • Demo
    • GitHub Repo
  • Angular Feature Flags – Michael Taranto
    • “An AngularJS module that allows you to control when you release new features in your app by putting them behind feature flags/switches. This module only supports Angular v1.2 and up. The basic premise is you write your feature and wrap it up in a directive, then where you implement that directive in your markup you add the feature-flag directive to the same element. You can then pass the key of the flag to this directive to resolve whether of not this feature should be enabled.”
    • GitHub Repo
  • Ember Feature Flags – Kate Gengler
    • “An ember-cli addon to provide feature flags. This addon injects a property features onto your routes, controllers and components.”
    • GitHub Repo
  • Ember Feature Flag Guide – Ember
    • “When a new feature is flagged it is only available in canary builds (if enabled at runtime). When it is time for the next beta cycle to be started (generally 6-12 week cycles) each feature will be evaluated and those features that are ready will be enabled in the next beta (and subsequently automatically enabled in all future canary builds). If a given feature is deemed unstable it will be disabled in the next beta point release, and not be included in the next stable release. It may still be included in the next beta cycle if the issues/concerns have been resolved. Once the beta cycle has completed the final release will include any features that were enabled during that cycle. At this point the feature flags will be removed from the canary and future beta branches, and the feature flag will no longer be used.”
    • GitHub Repo
  • Flux Feature Flags – Dave King
    • “An example of using the Flux application architecture to make amazing feature flags.”
    • GitHub Repo
  • Feature Toggles – Eric Elliot
    • “A painless feature toggle system in JavaScript. Decouple development and deployment.”
    • GitHub Repo
  • NPM Feature Toggles – Alex Lawrence
    • “A painless feature toggle system in JavaScript. Decouple development and deployment.”
    • GitHub Repo
  • React Feature Toggles – Parallel Drive
    • “React Feature Toggles attempts to satisfy the following requirements:
      • Universal – server and client side
      • Conditionally render components based on the presence or absence of a specific feature”
    • GitHub Repo