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

pairing-partners

v1.2.1

Published

a simple script for generating code pairings for your team

Downloads

6

Readme

pairing-partners

This is a simple tool for creating random pairing assignments for a team of software engineers. It reads from env vars to get the team it is using as a seed. See future work for some expansion that would be nice...

For now it outputs a nice-ish formatted message with the names in it.

Setup

  1. install with npm i -g pairing-partners
  2. add a comma-delimited list of your team's slackhandles/names to your env vars. It must be named TEAM. export TEAM="luke,han,leia,chewy,darth vader,r2d2". The easiest thing to do is to put this in your .bashrc/.zshrc or some other file that is sourced into your terminal's environment.
  3. that's it!

Usage

Usage:
  pairing-partners [--no-slack, -ns] [--help, -h] [--exclude, -e <list-here>] [--minimumSize, -m <size-here>] [--frequency, -f <string>]
  pps [--no-slack, -ns] [--help, -h] [--exclude, -e <list-here>] [--minimumSize, -m <size-here>] [--frequency, -f <string>]

--no-slack, -ns
  This disables the @ sign prefix. By default it adds this to make it easy to
  post the pairing into slack to let people know. But if you don't need that
  then use this argument to turn that off.

--help, -h
  Outputs this helpful help file.

--team, -t
  Outputs the team list and not the pairing assignments.

--exclude, -e
  Takes a commadelimited list of team members to exclude from the pairings.
  For example --exclude lando,luke
  Would exclude Lando and Luke from pairing generation.

--minimumSize, -m
  Tell it how many people you want as the minimum size for pairing groups.
  `-ms 3` means no group will be smaller than 3.

--frequency, -f
  Provide an alternate string for the message at the top of the pairing
  groups
  Pairing Partners for the {frequency} :party: :pairing:

Futures plans

  1. add contributor docs
  2. add the ability to publish straight to slack with something like slack-pipe
  3. add unit tests
  4. add a config file instead of env vars as an option for storing config
  5. Other things?