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 🙏

© 2025 – Pkg Stats / Ryan Hefner

file-diffy

v1.0.2

Published

## The need We were using a mono-repo on our clientside app (using `lerna.js`). While we had an affective way of running only packages that have been changed, each package had in it some files that were mobile only, and some files that were web only,

Readme

file-diffy

The need

We were using a mono-repo on our clientside app (using lerna.js).
While we had an affective way of running only packages that have been changed, each package had in it some files that were mobile only, and some files that were web only, that were in the relevant directories i.e package-a/web/file.js and package-a/mobile/file.js.

Our CI (Teamcity) was triggering all the mobile and web tests on every change in a package. We thought this is wasteful since if I only touched files that were affecting web/mobile.

The solution

Initially we created a bash script, that got a bit dirty and complicated with grep's and sed's. So I decided to create a simple node CLI tool that will accept a bunch of file names from the incoming Pull Request (these file names should be available either in your CI or using a simple git command), and output only the "types" that were changed, based on whatever types you have.
For example ['web', 'mobile] or ['common', 'docs'] etc.

How we use it

In Teamcity, we added a step before running the mobile/web tests, which runs the CLI tool, and then skips the next steps depending on the output. Check out the example in example.sh.

Quick Usage

input:

npm i -g file-diffy

file-diffy run --tokens web mobile docs --files="packages/package/web/index.js packages/src/mobile.index.ts packages/common/stuff.js"

output:

web mobile other # Notice that 'other' is also there, because a file not belonging to any token was found

How it works

file-diffy is based around the Regex command [^ ]*[\/|\.| ]<token>[\/|\.][^ ]*
Meaning it will generally search for directory paths and file names containing your token. Its also designed not to catch paths like package/shweb/file.js when searching for web for example.
It will also create a category called other incase you're interested to know that some files didn't belong to any token.

Options

--tokens space separated tokens which you want to run file-diffy on
--files space separated list of file names
--outputType will let you choose between json, txt, log, if json/text is chosen, a output.txt or output.json will be created