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

@runebreak/patch-builder

v0.1.5

Published

Utilities for building RGX patch artifacts (PatchSet generation, md5 index, throttled sampleroot server, and vendored librsync CLI)

Downloads

445

Readme

RGX Patch Builder Utilities

This repo contains a small set of Node.js scripts used to build and serve patch artifacts.

Published CLI commands:

  • patch-builder — generates PatchSet entries (patch deltas + download/delete ops) for a patch root.
  • update-md5filejson — generates or updates a files.json md5/size index for a directory.
  • librsync-cli — minimal CLI wrapper over @runebreak/librsync-bundled.
  • throttle-server — throttled static server with Range support.

Setup

npm install

Librsync

scripts/librsync-cli.ts expects @runebreak/librsync-bundled to be installed.

Usage

Downstream type imports

When installed as a dependency, patch plan types are exported from the package:

import type { PatchPlanFile, PatchSet } from '@runebreak/patch-builder';
// or
import type { PatchPlanFile, PatchSet } from '@runebreak/patch-builder/patch-type';

Downstream CLI usage

Install the package:

npm i @runebreak/patch-builder

Run the CLI directly:

npx patch-builder ./patch-root

If you specifically want npm run patch-builder in the consuming project, add a script there:

{
  "scripts": {
    "patch-builder": "patch-builder"
  }
}

Then run:

npm run patch-builder -- ./patch-root

Build a PatchSet for a patch root

Patch root layout expected by patch-builder:

  • <root>/files/user supplied new/current client files
  • <root>/files.jsongenerated previous index (will be updated)
  • <root>/_archive/generated basis/source files for delta/patch generation
  • <root>/.patchedfilesuser supplied gitignore-style allowlist patterns (relative, posix-style) to consider for delta/patch generation. generated patches then go in /patches/ and the source of the generation goes in _archive
  • <root>/.configuser supplied gitignore-like patterns identifying config file paths under files/. You should place items in here that you want to be able to 'force update' as well as 'update defaults'.
  • <root>/_defaults/generated materialized default config store (merged over time); default config baselines keep .default in the filename
  • <root>/patches/ — generated delta/patch files and config deltas
patch-builder /path/to/patch-root

Caution

Do not add an already distributed file to .patchedfiles and .config files after the fact. If you want to now patch it, it's best to delete it, build the updated patchset, re-add it, generate the updated patchset. Then you can do patching operations normally. However doing this with config files will delete the config file from the local side, so it's best to know ahead of time what files you want to manage default configs for.

Throttled sampleroot server (for testing)

Serve the included sampleroot with throttling:

throttle-server ./sampleroot 8069 200

There is also a VS Code workspace task to run this (see Throttle serve sampleroot (port 8069)).

Notes/Credits

Partially built via GPT-5(.3-Codex).