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

not-so-random

v0.3.0

Published

Library that allow applying rules to extract random items of an array

Readme

not-so-random

Lib allowing to use rules to configuration the extraction of random members of an array.

Build Status Coverage Status

Usage example

import notSoRandom from 'not-so-random';

var data = [
    { "name": "Stewie", "show": "Family Guy" },
    { "name": "Brian", "show": "Family Guy" },
    { "name": "Peter", "show": "Family Guy" },
    { "name": "Lois", "show": "Family Guy" },
    { "name": "Meg", "show": "Family Guy" },
    { "name": "Chris", "show": "Family Guy" },
    { "name": "Homer", "show": "The Simpsons" },
    { "name": "Marge", "show": "The Simpsons" },
    { "name": "Bart", "show": "The Simpsons" },
    { "name": "Lisa", "show": "The Simpsons" },
    { "name": "Maggie", "show": "The Simpsons" }
]

var rules = [
    {
        count: 2,
        test: function(character) { return character.show == "The Simpsons"; }
    },
    {
        count: 3,
        test: function(character) { return character.show == "Family Guy"; }
    }
]

// Will generate an array with 2 characters from the
// Simpsons and 3 from Family Guy
var randomCharacters = notSoRandom(data, rules);

Why is it cool ?

This lib is useful when several rules match the same items and can cause a rule to not have enough candidates. not-so-random will decide in which order to run the rules in order to allow every rules to have enough candidates.

Here is an example :


var data = [
    { "id": 1, "tags": ["foo", "bar"] },
    { "id": 2, "tags": ["foo"] },
    { "id": 3, "tags": ["foo"] },
    { "id": 4, "tags": ["bar"] }
]

var rules = [
    {
        count: 2,
        test: function(doc) { return doc.tags.indexOf("foo") >= 0; }
    },
    {
        count: 2,
        test: function(doc) { return doc.tags.indexOf("bar") >= 0; }
    }
]

If the first rule was blindly executed first and randomly matched the document with id 1, the second rule would not have enough candidates to match 2 items. Since the data allows the 2 rules to find enough matches, not-so-random determines in which order to run the rules to find a possible extraction.

Work In progress

This project is still Work In progress TODO :

  • unit testing
  • Docs