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

@wpelevator/subtree-split

v0.2.3

Published

Split the history of a directory into its own commits, with the same commit hashes as git subtree split

Readme

subtree-split

Split a directory of a monorepo into its own history, with the same commit hashes as git subtree split, in about a tenth of a second instead of several seconds.

In a monorepo with 477 commits, git subtree split takes 6 to 8 seconds for one package and subtree-split takes 0.1 seconds. On WordPress/gutenberg (43,568 commits) it splits packages/components in 1.7 seconds. The hashes are the same as git subtree split makes, so a repository that you already split that way keeps its history when you switch.

@wpelevator/wp-release uses it for deploy git --split-prefix. The detailed documentation lives in this package's docs/ directory. The monorepo docs site builds it for wpelevator.github.io/docs/js/subtree-split/latest/ and includes released versions whose tags contain docs.

Quick start

Run it in the monorepo, with the directory that you want to split:

npx @wpelevator/subtree-split --prefix packages/my-library

It prints the hash of the split commit and writes the commits to the repository. It doesn't change a branch, so you decide what to do with the hash. To publish it to the repository of the package:

tip=$(npx @wpelevator/subtree-split --prefix packages/my-library)
git push [email protected]:acme/my-library.git "$tip:refs/heads/main"

To keep it in a local branch instead, run git update-ref refs/heads/split/my-library "$tip".

It needs Node.js 22.12 or later, Git 2.29 or later, and the full history of the repository. It works in a bare clone, and it fails with a message on a shallow one, so in CI check out with fetch-depth: 0.

See the CLI page for the options, GitHub Actions for workflows, caching to speed up repeated runs, the library API for JavaScript, and compatibility for the limits and how the hashes match git subtree split.

Develop

See development.

License

MIT