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

swgh

v1.0.4

Published

SWGH - Split With Git History. An NPX command which allows you to quickly split a file into a copy of it, retaining its git history.

Downloads

2

Readme

SWGH - Split With Git History

An minimal NPX command which allows you to quickly & easily clone a file into a copy of it, retaining its git history.

It's most useful when you have a file and you want to break it up into multiple smaller files, retaining the line git history in each of them.

Usage

npx swgh <source> <destination>

Examples

npx swgh README.md README2.md

npx swgh README.md cloneWithOtherExtension.txt

npx swgh someFolder/someFile.js someOtherFolder/randomSubfolder/halfOfTheFile.ts

Let's assume you have a big file characters.js containing many functions which log a character, and you'd like to split it up into 2 files. One for consonant loggers, one for vowel loggers.

$ git blame characters.js

  ca123d function a() { console.log('a') }
  b5103d function b() { console.log('b') }
  b5103d function c() { console.log('c') }
  b5103d function d() { console.log('d') }
  ca123d function e() { console.log('e') }
  ...

Assume that in commit ca123d vowel loggers have been added and in commit b5103d consonant loggers have been added.

  $ npx swgh characters.js vowelLoggers.js

The result is characters.js and vowelLoggers.js containing the exact same code with the same git history.

Rename the original file to consonantLoggers.js

mv characters.js consonantLoggers.js

Clean up the files to represent what you initially intended:

$ git blame consonantLoggers.js

  b5103d function b() { console.log('b') }
  b5103d function c() { console.log('c') }
  b5103d function d() { console.log('d') }
  ...
$ git blame vowelLoggers.js

  ca123d function a() { console.log('a') }
  ca123d function e() { console.log('e') }
  ...

Commit your changes

$ git commit -am "Splitted up characters.js into consonantLoggers.js and vowelLoggers.js"

Caveats

  • You can only use this command within a GIT repository
  • You should not have any uncommitted changes. git status should say "nothing to commit, working tree clean"
  • When the command is executed it will create 3-4 new commits, due the internal process