Your module to handle with feature toggles in ReactJS applications easier

Usage no npm install needed!

<script type="module">
  import reactorFeatureToggle from '';


Reactor feature toggle

Greenkeeper badge npm

npm version npm downloads

Build Status Coverage Status Dependency Status


Your module to handle with feature toggles in ReactJS applications easier.

Why Feature toggle?

This is a common concept, but why use this directive instead solve it via server-side rendering?

The idea of this directive is make this process transparent and easier. So the main point is integrate this directive with other tooling process, such as:

  • Server-side rendering;
  • Progressive rendering;
  • Any other that yoy like :)

You can integrate with WebSockets or handling this in a EventSourcing architecture. It's totally transparent for you and you can integrate easier in your application.


You can get it on NPM installing reactor-feature-toggle module as a project dependency.

npm install reactor-feature-toggle --save
# or
yarn add reactor-feature-toggle

You can also use the standalone UMD build by including dist/reactor-feature-toggle.js in your page. If you do this you'll also need to include the dependencies. For example:

<script src="<package-version></package-version>/dist/react.js"></script>
<script src="<package-version>/dist/react-dom.js"></script>
<script src=""></script>


You'll need to import FeatureToggleProvider and add it into the root component of your application. So that you can enable/disable features via FeatureToggle component any place in your application.

Also, multiple FeatureToggleProvider are allowed, which gives more flexibility for your application.

import React, { Component } from 'react';
import { FeatureToggleProvider, FeatureToggle } from 'reactor-feature-toggle';

const AppWrapper = () => {
  const featureToggleData = {
    enableMainContent: true,
    enableDescriptionContent: true,
    enableSecondContent: false,

  return (
    <FeatureToggleProvider featureToggleService={featureToggleData}>
        <FeatureToggle featureName={'enableMainContent'}>
          <div className="content">
            <p>This content is enabled</p>
            <FeatureToggle featureName={'enableSecondContent'}>
              <p>This content is disabled</p>
            <FeatureToggle featureName={'!enableSecondContent'}>
                This content is disabled, but should be displayed since it has
                `!` prefix at `featureName`

          featureName={['enableMainContent', 'enableDescriptionContent']}
          <div className="content">
              This content is enabled since `enableMainContent` and
              `enableDescriptionContent` are both truthly

          featureName={['enableMainContent', '!enableDescriptionContent']}
          <div className="content">
              This content is disabled because `enableMainContent` is truthly
              and `enableSecondContent` is falsy when using `!` prefix on array
              of configuration passed via props.
              This can be used as a fallback if both feature toggles are not
              enabled, as an example

export default AppWrapper;


Try out the demo!


this project is using np package to publish, which makes things straightforward. EX: np <patch|minor|major>

For more details, please check np package on


Wilson Mendes (willmendesneto)