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

mc-matching

v0.0.4

Published

starter template for a rollup library

Readme

TODO

  • [] add types
  • [] add benchmarks
  • [] optimize
    • [] performance (in addition to doing more work in a single loop, maybe make webworker friendly)
    • [] memory (maybe generators/iterators for large sets?)

Overview

// Step 0 - Have students and mentors
type Student = { id: any, ...attributes };
type Mentor = { id: any, ...attributes };

students = Student[]
mentors = Mentor[]

// STEP 1 - For each student, rank each mentor
type RankedCandidate = { id: (Student | Mentor).id, score: number }
type Weights = { string: number } // { major: -5, hobbies: -3 }
type Required = [keyof Weight] // ['major'] if required is passed, majors MUST match between student and mentor
{
  students: (Student & { RankedCandidate[] })[],
  mentors: (Mentor & { RankedCandidate[] })[]
} = rank({ students, mentors, weights, required }) // <- returns sorted lowest score to highest (lowest is best)

// STEP 2 - Format for matching (strip score)
type Picks = {
  [Student.id]: Array<Mentor.id>;
  [Mentor.id]: Array<Student.id>;
}
studentsPicks: Picks  = students.map(({id}) => id)
mentorsPicks: Picks = mentors.map(({id}) => id)

// STEP 2.5
// if we want even distribution across mentors (i.e. don't fill mentors up to capacity immediately),
// we can split the remaining steps into multiple passes.
// instead of having mentor with capacity 3, we triplicate that mentor with capacity 1.
// if 3 is the maximum capcity (across all mentors), we do 3 runs with no duplicate mentors in each run.
// we pass the remaining, unmatched students from the 1st run to the 2nd run and from the 2nd run to the 3rd run.

// STEP 3 - Format Mentor capacities
type Capacities = { [Mentor.id]: number }
const capacities: Capacities = { 100: 1, 101: 2, 102: 2, 103: 2 };

// STEP 4 - match
// take best matches - see algo https://github.com/sammynave/mc-matching/blob/main/src/match.ts

// STEP 5 - format to present to user?