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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@whyrify/whyrify-js

v1.0.1

Published

Whyrify fault injection engine

Readme

Whyrify

Fault injection engine for whyrify.com

Inject and configure

inject snippet to website, make it not async and load as early as you can:

<script type="text/javascript" src="//s.whyrify.com/w/whyrify.min.js" />

Using WHYRIFY_CONFIG object, you can setup reporting, and fault rate (default to 5%).

<script>
  window.whyrify = window.whyrify || function() {
    (window.whyrify.q = window.whyrify.q || []).push(arguments);
  };
  whyrify('config', 'XXXX-XXXX-XXXX-XXXX-XXXX-XXXX', 0.5);
</script>
<script type="text/javascript" src="//s.whyrify.com/w/whyrify.js" />

Fault injection

Now all scripts marked with type="text/whyrify" will run by whyrify.js, eventually fail with controlled chance. Additionally you can name the feature/attribute by adding attribute data-feature="feature-x".

For example:

<script type="text/whyrify" src="https://www.googletagmanager.com/gtm.js?id='XXXXX" data-feature="GTM" />

You can also call decide to bucket feature manually:

<script>
  window.whyrify = window.whyrify || function() {
    (window.whyrify.q = window.whyrify.q || []).push(arguments);
  };
  window.whyrify("decide", "featureX", (result) => {
      if(result === "control") {
          //activate feature
      }
  });
</script>
<script type="text/javascript" src="//s.whyrify.com/w/whyrify.min.js" />

Measure

Finally, you can send conversion events by calling whyrify('link', 'conversion'), so we can validate experiment using Bayesian stats.

window.whyrify =
    window.whyrify ||
    function () {
        (window.whyrify.q = window.whyrify.q || []).push(arguments);
    };
window.whyrify("link", "conversion"); //trigger  default conversion
window.whyrify("link", "add-to-cart"); // trigger another conversion

How to use as NPM package

Install the package:

npm i @whyrify/whyrify-js

Basic usage:

import { Whyrify } from "@whyrify/whyrify-js";

const faultEngine = new Whyrify(
    "XXXX-XXXX-XXXX-XXXX-XXXX-XXXX", // measurement id
    50, // 50% chance to fail
    true, //do not watch for another scripts
);
if (faultEngine.decide("fault-injection-hero") === "control") {
    console.log("Control");
} else {
    console.log("Fault");
}
faultEngine.link("conversion");