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

dominium

v0.2.11

Published

Break large changes into smaller ones based on mandatory reviewer coverage.

Downloads

31

Readme

dominium

Break large changes into smaller ones based on mandatory reviewer coverage.

Install

  1. npm i -g dominium
  2. Install ripgrep

Usage

Run dominium in the root of your git repo to split up your last commit. Your commit message and branch name are used when creating new branches.

~/myGitRepo[eslint-fix]$ git commit -am "eslint --fix accross entire codebase"
~/myGitRepo[eslint-fix]$ dominium
Splitting code into 4 branches:

  [eslint-fix-1] 12 files owned by noah.sugarman, airbnb/someteam
  [eslint-fix-2] 10 files owned by bob-youruncle, amy-lobg
  [eslint-fix-3] 14 files owned by airbnb/uncles
  [eslint-fix-4] 9 files owned by no owner

Proceed? [Y/n] Y

Creating branch eslint-fix-1
Creating branch eslint-fix-2
Creating branch eslint-fix-3
Creating branch eslint-fix-4

Done
~/myGitRepo[eslint-fix]$ git log eslint-fix-1 --oneline -1
7c89b7bb5bd eslint --fix accross entire codebase 1/4

Options

--owners-file [name] name of file containing list of owners, default MANDATORY_REVIEWERS

--max-branch-files [max] max number of files per branch, default Infinity

Limitations / TODOs

  • Doesn't read file comments such as // MANDATORY_REVIEWERS noah bob.
  • Unhelpful error messages.
  • Only supports git repos.
  • Doesn't know who belongs to which team, which would allow a smarter pull request coverage algorithm.
  • Doesn't work if OWNERS file contains information other than teams and usernames.