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

rbs-react-ab-test

v2.3.3

Published

A/B testing React components and debug tools. Isomorphic with a simple, universal interface. Well documented and lightweight. Tested in popular browsers and Node.js. Includes helpers for Mixpanel and Segment.com.

Downloads

5

Readme

A/B Testing React Components

NPM version Circle CI Dependency Status NPM Downloads

Wrap components in <Variant /> and nest in <Experiment />. A variant is chosen randomly and saved to local storage.

<Experiment name="My Example">
  <Variant name="A">
    <div>Version A</div>
  </Variant>
  <Variant name="B">
    <div>Version B</div>
  </Variant>
</Experiment>

Report to your analytics provider using the emitter. Helpers are available for Mixpanel and Segment.com.

emitter.addPlayListener((experimentName, variantName) => {
  mixpanel.track("Start Experiment", {
    name: experimentName,
    variant: variantName
  });
});

Please ★ on GitHub!

Installation

react-ab-test is compatible with React >=0.14.x

yarn add @marvelapp/react-ab-test

Usage

Web setup

import React from "react";
import ReactDOM from "react-dom";
import "./index.css";
import App from "./App";
import * as serviceWorker from "./serviceWorker";
import { Provider, store } from "@marvelapp/react-ab-test";

const s = store.configureStore(window.localStorage);

ReactDOM.render(
  <Provider.ABProvider store={s}>
    <App />
  </Provider.ABProvider>,
  document.getElementById("root")
);

Native setup

import React from "react";
import { StyleSheet, Text, View } from "react-native";
import { AsyncStorage } from "react-native";

import { store, Provider, Experiment, Variant } from "@marvelapp/react-ab-test";

const s = store.configureStore(AsyncStorage);

export default function App() {
  return (
    <Provider.ABProvider store={s}>
      <View>
        <Experiment name="My Example">
          <Variant name="A">
            <Text>Version A</Text>
          </Variant>
          <Variant name="B">
            <Text>Version B</Text>
          </Variant>
        </Experiment>
      </View>
    </Provider.ABProvider>
  );
}

const styles = StyleSheet.create({
  container: {
    flex: 1,
    backgroundColor: "#fff",
    alignItems: "center",
    justifyContent: "center"
  }
});

Standalone Component

Try it on JSFiddle

import React from "react";
import { Experiment, Variant, emitter } from "@marvelapp/react-ab-test";

class App extends Component {
  onButtonClick(e) {
    this.refs.experiment.win();
  }
  render() {
    return (
      <div>
        <Experiment ref="experiment" name="My Example">
          <Variant name="A">
            <div>Section A</div>
          </Variant>
          <Variant name="B">
            <div>Section B</div>
          </Variant>
        </Experiment>
        <button onClick={this.onButtonClick}>Emit a win</button>
      </div>
    );
  }
}

// Called when the experiment is displayed to the user.
emitter.addPlayListener(function(experimentName, variantName) {
  console.log(`Displaying experiment ${experimentName} variant ${variantName}`);
});

// Called when a 'win' is emitted, in this case by this.refs.experiment.win()
emitter.addWinListener(function(experimentName, variantName) {
  console.log(
    `Variant ${variantName} of experiment ${experimentName} was clicked`
  );
});

Coordinate Multiple Components

Try it on JSFiddle

import React from 'react';
import { Experiment, Variant, emitter } from '@marvelapp/react-ab-test';

// Define variants in advance.
emitter.defineVariants('My Example', ['A', 'B', 'C']);

function Component1 = () => {
  return (
    <Experiment name="My Example">
      <Variant name="A">
        <div>Section A</div>
      </Variant>
      <Variant name="B">
        <div>Section B</div>
      </Variant>
    </Experiment>
  );
};

const Component2 = () => {
  return (
    <Experiment name="My Example">
      <Variant name="A">
        <div>Subsection A</div>
      </Variant>
      <Variant name="B">
        <div>Subsection B</div>
      </Variant>
      <Variant name="C">
        <div>Subsection C</div>
      </Variant>
    </Experiment>
  );
};

class Component3 extends React.Component {
  onButtonClick(e) {
    emitter.emitWin('My Example');
  }
  render() {
    return <button onClick={this.onButtonClick}>Emit a win</button>;
  }
}

const App = () => {
  return (
    <div>
      <Component1 />
      <Component2 />
      <Component3 />
    </div>
  );
};

// Called when the experiment is displayed to the user.
emitter.addPlayListener(function(experimentName, variantName) {
  console.log(`Displaying experiment ${experimentName} variant ${variantName}`);
});

// Called when a 'win' is emitted, in this case by this.refs.experiment.win()
emitter.addWinListener(function(experimentName, variantName) {
  console.log(
    `Variant ${variantName} of experiment ${experimentName} was clicked`
  );
});

Weighting Variants

Try it on JSFiddle

Use emitter.defineVariants() to optionally define the ratios by which variants are chosen.

import React from "react";
import { Experiment, Variant, emitter } from "@marvelapp/react-ab-test";

// Define variants and weights in advance.
emitter.defineVariants("My Example", ["A", "B", "C"], [10, 40, 40]);

const App = () => {
  return (
    <div>
      <Experiment ref="experiment" name="My Example">
        <Variant name="A">
          <div>Section A</div>
        </Variant>
        <Variant name="B">
          <div>Section B</div>
        </Variant>
        <Variant name="C">
          <div>Section C</div>
        </Variant>
      </Experiment>
    </div>
  );
};

Force variant calculation before rendering experiment

There are some scenarios where you may want the active variant of an experiment to be calculated before the experiment is rendered. To do so, use emitter.calculateActiveVariant(). Note that this method must be called after emitter.defineVariants()

import { emitter } from "@marvelapp/react-ab-test";

// Define variants in advance
emitter.defineVariants("My Example", ["A", "B", "C"]);
emitter.calculateActiveVariant("My Example", "userId");

// Active variant will be defined even if the experiment is not rendered
const activeVariant = emitter.getActiveVariant("My Example");

Debugging

The debugger attaches a fixed-position panel to the bottom of the <body> element that displays mounted experiments and enables the user to change active variants in real-time.

The debugger is wrapped in a conditional if(process.env.NODE_ENV === "production") {...} and will not display on production builds using envify.

Try it on JSFiddle

import React from "react";
import {
  Experiment,
  Variant,
  experimentDebugger
} from "@marvelapp/react-ab-test";

experimentDebugger.enable();

const App = () => {
  return (
    <div>
      <Experiment ref="experiment" name="My Example">
        <Variant name="A">
          <div>Section A</div>
        </Variant>
        <Variant name="B">
          <div>Section B</div>
        </Variant>
      </Experiment>
    </div>
  );
};

Server Rendering

A <Experiment /> with a userIdentifier property will choose a consistent <Variant /> suitable for server side rendering.

See ./examples/isomorphic for a working example.

Example

The component in Component.jsx:

var React = require("react");
var Experiment = require("react-ab-test/lib/Experiment");
var Variant = require("react-ab-test/lib/Variant");

module.exports = React.createClass({
  propTypes: {
    userIdentifier: React.PropTypes.string.isRequired
  },
  render: function() {
    return (
      <div>
        <Experiment
          ref="experiment"
          name="My Example"
          userIdentifier={this.props.userIdentifier}
        >
          <Variant name="A">
            <div>Section A</div>
          </Variant>
          <Variant name="B">
            <div>Section B</div>
          </Variant>
        </Experiment>
      </div>
    );
  }
});

We use a session ID for the userIdentifier property in this example, although a long-lived user ID would be preferable. See server.js:

require("babel/register")({ only: /jsx/ });

var express = require("express");
var session = require("express-session");
var React = require("react");
var ReactDOMServer = require("react-dom/server");
var Component = require("./Component.jsx");
var abEmitter = require("react-ab-test/lib/emitter");

var app = express();

app.set("view engine", "ejs");

app.use(
  session({
    secret: "keyboard cat",
    resave: false,
    saveUninitialized: true
  })
);

app.get("/", function(req, res) {
  var reactElement = React.createElement(Component, {
    userIdentifier: req.sessionID
  });
  var reactString = ReactDOMServer.renderToString(reactElement);
  abEmitter.rewind();
  res.render("template", {
    sessionID: req.sessionID,
    reactOutput: reactString
  });
});

app.use(express.static("www"));

app.listen(8080);

Remember to call abEmitter.rewind() to prevent memory leaks.

An EJS template in template.ejs:

<!DOCTYPE html>
<html>
  <head>
    <title>Isomorphic Rendering Example</title>
  </head>
  <script type="text/javascript">
    var SESSION_ID = <%- JSON.stringify(sessionID) %>;
  </script>
  <body>
    <div id="react-mount"><%- reactOutput %></div>
    <script type="text/javascript" src="bundle.js"></script>
  </body>
</html>

On the client in app.jsx:

var React = require("react");
var ReactDOM = require("react-dom");
var Component = require("../Component.jsx");

var container = document.getElementById("react-mount");

ReactDOM.render(<Component userIdentifier={SESSION_ID} />, container);

With Babel

Code from ./src is written in JSX and transpiled into ./lib using Babel. If your project uses Babel you may want to include files from ./src directly.

Alternative Libraries

Please let us know about alternate libraries not included here.

Resources for A/B Testing with React

Please let us know about React A/B testing resources not included here.

API Reference

<Experiment />

Experiment container component. Children must be of type Variant.

  • Properties:
    • name - Name of the experiment.
      • Required
      • Type: string
      • Example: "My Example"
    • userIdentifier - Distinct user identifier. When defined, this value is hashed to choose a variant if defaultVariantName or a stored value is not present. Useful for server side rendering.
      • Optional
      • Type: string
      • Example: "7cf61a4521f24507936a8977e1eee2d4"
    • defaultVariantName - Name of the default variant. When defined, this value is used to choose a variant if a stored value is not present. This property may be useful for server side rendering but is otherwise not recommended.
      • Optional
      • Type: string
      • Example: "A"

<Variant />

Variant container component.

  • Properties:
    • name - Name of the variant.
      • Required
      • Type: string
      • Example: "A"

emitter

Event emitter responsible for coordinating and reporting usage. Extended from facebook/emitter.

emitter.emitWin(experimentName)

Emit a win event.

  • Return Type: No return value
  • Parameters:
    • experimentName - Name of an experiment.
      • Required
      • Type: string
      • Example: "My Example"

emitter.addActiveVariantListener([experimentName, ] callback)

Listen for the active variant specified by an experiment.

  • Return Type: Subscription
  • Parameters:
    • experimentName - Name of an experiment. If provided, the callback will only be called for the specified experiment.
      • Optional
      • Type: string
      • Example: "My Example"
    • callback - Function to be called when a variant is chosen.
      • Required
      • Type: function
      • Callback Arguments:
        • experimentName - Name of the experiment.
          • Type: string
        • variantName - Name of the variant.
          • Type: string

emitter.addPlayListener([experimentName, ] callback)

Listen for an experiment being displayed to the user. Trigged by the React componentWillMount lifecycle method.

  • Return Type: Subscription
  • Parameters:
    • experimentName - Name of an experiment. If provided, the callback will only be called for the specified experiment.
      • Optional
      • Type: string
      • Example: "My Example"
    • callback - Function to be called when an experiment is displayed to the user.
      • Required
      • Type: function
      • Callback Arguments:
        • experimentName - Name of the experiment.
          • Type: string
        • variantName - Name of the variant.
          • Type: string

emitter.addWinListener([experimentName, ] callback)

Listen for a successful outcome from the experiment. Trigged by the emitter.emitWin(experimentName) method.

  • Return Type: Subscription
  • Parameters:
    • experimentName - Name of an experiment. If provided, the callback will only be called for the specified experiment.
      • Optional
      • Type: string
      • Example: "My Example"
    • callback - Function to be called when a win is emitted.
      • Required
      • Type: function
      • Callback Arguments:
        • experimentName - Name of the experiment.
          • Type: string
        • variantName - Name of the variant.
          • Type: string

emitter.defineVariants(experimentName, variantNames [, variantWeights])

Define experiment variant names and weighting. Required when an experiment spans multiple components containing different sets of variants.

If variantWeights are not specified variants will be chosen at equal rates.

The variants will be chosen according to the ratio of the numbers, for example variants ["A", "B", "C"] with weights [20, 40, 40] will be chosen 20%, 40%, and 40% of the time, respectively.

  • Return Type: No return value
  • Parameters:
    • experimentName - Name of the experiment.
      • Required
      • Type: string
      • Example: "My Example"
    • variantNames - Array of variant names.
      • Required
      • Type: Array.<string>
      • Example: ["A", "B", "C"]
    • variantWeights - Array of variant weights.
      • Optional
      • Type: Array.<number>
      • Example: [20, 40, 40]

emitter.setActiveVariant(experimentName, variantName)

Set the active variant of an experiment.

  • Return Type: No return value
  • Parameters:
    • experimentName - Name of the experiment.
      • Required
      • Type: string
      • Example: "My Example"
    • variantName - Name of the variant.
      • Required
      • Type: string
      • Example: "A"

emitter.getActiveVariant(experimentName)

Returns the variant name currently displayed by the experiment.

  • Return Type: string
  • Parameters:
    • experimentName - Name of the experiment.
      • Required
      • Type: string
      • Example: "My Example"

emitter.calculateActiveVariant(experimentName [, userIdentifier, defaultVariantName])

Force calculation of active variant, even if the experiment is not displayed yet. Note: This method must be called after emitter.defineVariants

  • Return Type: string
  • Parameters:
    • experimentName - Name of the experiment.
      • Required
      • Type: string
      • Example: "My Example"
    • userIdentifier - Distinct user identifier. When defined, this value is hashed to choose a variant if defaultVariantName or a stored value is not present. Useful for server side rendering.
      • Optional
      • Type: string
      • Example: "7cf61a4521f24507936a8977e1eee2d4"
    • defaultVariantName - Name of the default variant. When defined, this value is used to choose a variant if a stored value is not present. This property may be useful for server side rendering but is otherwise not recommended.
      • Optional
      • Type: string
      • Example: "A"

emitter.getSortedVariants(experimentName)

Returns a sorted array of variant names associated with the experiment.

  • Return Type: Array.<string>
  • Parameters:
    • experimentName - Name of the experiment.
      • Required
      • Type: string
      • Example: "My Example"

Subscription

Returned by the emitter's add listener methods. More information available in the facebook/emitter documentation.

subscription.remove()

Removes the listener subscription and prevents future callbacks.

  • Parameters: No parameters

experimentDebugger

Debugging tool. Attaches a fixed-position panel to the bottom of the <body> element that displays mounted experiments and enables the user to change active variants in real-time.

The debugger is wrapped in a conditional if(process.env.NODE_ENV === "production") {...} and will not display on production builds using envify. This can be overriden by setDebuggerAvailable

experimentDebugger.setDebuggerAvailable(isAvailable)

Overrides process.env.NODE_ENV check, so it can be decided if the debugger is available or not at runtime. This allow, for instance, to enable the debugger in a testing environment but not in production. Note that you require to explicitly call to .enable even if you forced this to be truthy.

  • Return Type: No return value
  • Parameters:
    • isAvailable - Tells whether the debugger is available or not
      • Required
      • Type: boolean

experimentDebugger.enable()

Attaches the debugging panel to the <body> element.

  • Return Type: No return value

experimentDebugger.disable()

Removes the debugging panel from the <body> element.

  • Return Type: No return value

mixpanelHelper

Sends events to Mixpanel. Requires window.mixpanel to be set using Mixpanel's embed snippet.

Usage

When the <Experiment /> is mounted, the helper sends an Experiment Play event using mixpanel.track(...) with Experiment and Variant properties.

When a win is emitted the helper sends an Experiment Win event using mixpanel.track(...) with Experiment and Variant properties.

Try it on JSFiddle

import React from "react";
import { Experiment, Variant, mixpanelHelper } from "@marvelapp/react-ab-test";

// window.mixpanel has been set by Mixpanel's embed snippet.
mixpanelHelper.enable();

class App extends React.Component {
  onButtonClick(e) {
    emitter.emitWin("My Example");
    // mixpanelHelper sends the 'Experiment Win' event, equivalent to:
    // mixpanel.track('Experiment Win', {Experiment: "My Example", Variant: "A"})
  }
  componentWillMount() {
    // mixpanelHelper sends the 'Experiment Play' event, equivalent to:
    // mixpanel.track('Experiment Play', {Experiment: "My Example", Variant: "A"})
  }
  render() {
    return (
      <div>
        <Experiment ref="experiment" name="My Example">
          <Variant name="A">
            <div>Section A</div>
          </Variant>
          <Variant name="B">
            <div>Section B</div>
          </Variant>
        </Experiment>
        <button onClick={this.onButtonClick}>Emit a win</button>
      </div>
    );
  }
}

mixpanelHelper.enable()

Add listeners to win and play events and report results to Mixpanel.

  • Return Type: No return value

mixpanelHelper.disable()

Remove win and play listeners and stop reporting results to Mixpanel.

  • Return Type: No return value

segmentHelper

Sends events to Segment. Requires window.analytics to be set using Segment's embed snippet.

Usage

When the <Experiment /> is mounted, the helper sends an Experiment Viewed event using segment.track(...) with experimentName and variationName properties.

When a win is emitted the helper sends an Experiment Won event using segment.track(...) with experimentName and variationName properties.

Try it on JSFiddle

import React from "react";
import { Experiment, Variant, segmentHelper } from "@marvelapp/react-ab-test";

// window.analytics has been set by Segment's embed snippet.
segmentHelper.enable();

class App extends React.Component {
  onButtonClick(e) {
    emitter.emitWin("My Example");
    // segmentHelper sends the 'Experiment Won' event, equivalent to:
    // segment.track('Experiment Won', {experimentName: "My Example", variationName: "A"})
  }
  componentWillMount() {
    // segmentHelper sends the 'Experiment Viewed' event, equivalent to:
    // segment.track('Experiment Viewed, {experimentName: "My Example", variationName: "A"})
  }
  render() {
    return (
      <div>
        <Experiment ref="experiment" name="My Example">
          <Variant name="A">
            <div>Section A</div>
          </Variant>
          <Variant name="B">
            <div>Section B</div>
          </Variant>
        </Experiment>
        <button onClick={this.onButtonClick}>Emit a win</button>
      </div>
    );
  }
}

segmentHelper.enable()

Add listeners to win and play events and report results to Segment.

  • Return Type: No return value

segmentHelper.disable()

Remove win and play listeners and stop reporting results to Segment.

  • Return Type: No return value

amplitudeHelper

Sends events to Amplitude.

Usage

When the <Experiment /> is mounted, the helper sends an Experiment Viewed event using [amplitude.logEvent(...) with experimentName and variationName properties.

When a win is emitted the helper sends an Experiment Won event using [amplitude.logEvent(...)] with experimentName and variationName properties.

import React from "react";
import { Experiment, Variant, amplitudeHelper } from "@marvelapp/react-ab-test";
import amplitude from "amplitude-js/amplitude";

const amplitudeInstance = amplitude.getInstance().init("amplitude key");

amplitudeHelper.enable(amplitudeInstance);

class App extends React.Component {
  onButtonClick(e) {
    emitter.emitWin("My Example");
    // segmentHelper sends the 'Experiment Won' event, equivalent to:
    // segment.track('Experiment Won', {experimentName: "My Example", variationName: "A"})
  }
  componentWillMount() {
    // segmentHelper sends the 'Experiment Viewed' event, equivalent to:
    // segment.track('Experiment Viewed, {experimentName: "My Example", variationName: "A"})
  }
  render() {
    return (
      <div>
        <Experiment ref="experiment" name="My Example">
          <Variant name="A">
            <div>Section A</div>
          </Variant>
          <Variant name="B">
            <div>Section B</div>
          </Variant>
        </Experiment>
        <button onClick={this.onButtonClick}>Emit a win</button>
      </div>
    );
  }
}

amplitudeHelper.enable(amplitudeInstance)

Add listeners to win and play events and report results to Amplitude.

  • Return Type: No return value

amplitudeHelper.disable()

Remove win and play listeners and stop reporting results to Amplitude.

  • Return Type: No return value

How to contribute

Requisites

Before contribuiting you need:

Then you can:

  • Apply your changes :sunglasses:
  • Build your changes with yarn build
  • Test your changes with yarn test
  • Lint your changes with yarn lint
  • And finally open the PR! :tada:

Running Tests

yarn test