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

empiricist

v0.1.0

Published

Empiricist is a utility library for organizing conditional rendering of experimental React components (for A/B testing or gradual releases) in a declarative way that would not affect the components structure, but instead allows to "patch" the components t

Downloads

3

Readme

Empiricist

Empiricist is a utility library for organizing conditional rendering of experimental React components (for A/B testing or gradual releases) in a declarative way that would not affect the components structure, but instead allows to "patch" the components tree in a minimalistic manner.

Usage

The package is can be installed from NPM using following command

npm install empiricist

# or if you use yarn

yarn add empiricist

When ready, we'll need to provide the active experiments to the Empiricist using the provider component:

import { Empiricist } from 'empiricist'

function App() {
  // some code here
  return (
    <Empiricist experiments={currentExperiments}>
      /* your components go here */
    </Empiricist>
  )
}

The currentExperiments is a simple dictionary { [key: string]: string }, that specifies the current experiments configuration.

Once that is done, you can use the experiment() function in places where components need to be rendered conditionally based on experiment value.

export const Example = experiment('example', DefaultExample)
  .withVariation('foo', MaybeBetterExample)
  .withVariation('bar', DifferentBetterExample)

If in the experiments object property example equals "foo", the MaybeBetterExample will be rendered. If it equals "bar", then DifferentBetterExample is rendered. In all other cases the default component is used.

Also, Example component now has props defined as intersection type of MaybeBetterExample and DifferentBetterExample props, which enables type safety if you're using TypeScript.

API Reference

experiment(id, DefaultComponent)

experiment(id: string, DefaultComponent?: React.ComponentType);

The function that is used to make the component experimental. If default component is not provided, "Null Component" will be used instead (i.e. nothing is rendered in default case).

withVariation

withVariation(id: string, VariationComponent: React.ComponentType);

The method can be used if there is a need to render one component instead of another.

withSiblingBefore

withSiblingBefore(id: string, SiblingComponent: React.ComponentType);

Unlike, the previous one, the method keeps the default component and, if the provided id matches the experiment value, renders the "sibling" right before the target component.

withSiblingAfter

withSiblingAfter(id: string, SiblingComponent: React.ComponentType);

Is similar to withSiblingBefore but the "sibling" is added after the target component.

withInnerWrapper(id, WrapperComponent)

withInnerWrapper(id: string, SiblingComponent: React.ComponentType);

Allows to optionally wrap the target component's children with the provided component.

withOuterWrapper(id, WrapperComponent)

withOuterWrapper(id: string, SiblingComponent: React.ComponentType);

Allows to optionally wrap the target component itself with the provided component.

FP Style API

Also, the library exports the unbound methods that can be applied to the experiment later.

  • applyVariation
  • applySiblingBefore
  • applySiblingAfter
  • applyInnerWrapper
  • applyOuterWrapper

It might be useful, when is used in FP-like pipe functions.

import { pipe } from 'fp-ts/function'

export const Greeting = pipe(
  experiment('greeting', DefaultGreeting),
  applyVariation('formal', FormalGreeting),
  applyVariation(
    'informal',
    pipe(
      experiment('emoji', InformalGreeting),
      applySiblingAfter('true', WavingHand)
    )
  )
);

Contribution

This project is a quick weekend POC, so it may not be stable enough to be used in production. But if you find any bugs or have improvements ideas, feel free to create issue or open a PR.