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

purposefile

v1.2.0

Published

Make sure every file in your repo is exactly where it should be

Readme

purposefile

Make sure every file in your repo is exactly where it should be.

Example of running purposefile CLI

Install

First, make sure node and npm are installed.

Then if you have an existing package.json you can run:

npm install --save-dev purposefile
npx purposefile

Or if you want to use it globally you can also just run:

npx purposefile

It's recommended that you save this to your package.json#scripts

{
	"name": "my-package",
	"scripts": {
		"check-files": "purposefile"
	}
}
npm run check-files

Usage

First create a .purposefile in the root of your project like this:

.purposefile                 Configures purposefile
.gitignore                   Configures git to ignore certain files
.prettierrc                  Configures Prettier
.prettierignore              Configures Prettier ignored files
package.json                 Configures npm and related tools
package-lock.json            Lock file for npm dependencies
tsconfig.json                Configures TypeScript
README.md                    Documentation for repo
LICENSE                      License for package
.git/**                      Internal git state & config
node_modules/**/*            Dependencies installed by npm
typings/*/*.d.ts             TypeScript library type definitions
src/**/*.ts                  Source files
!src/**/*.test.ts            Dont place test files within src/
test/**/*.test.ts            Test files
dist/**/*.{js,d.ts}{,.map}   Built source files
.github/*.png                Images for README

Note: Entries are matched in reverse order. Entries with no defined purpose or that start with a ! act like negations to the globs above them.

Then run:

npx purposefile

If all the files in the repo are known, you'll get:

Example output of purposefile when all files are known

Or if there's any unknown files:

Example output of purposefile when there are unknown files

If you want to check the purpose of a file you can run:

purposefile path/to/file

Example output of purposefile for a single file lookup

If you want to check the purpose of many files at once you can also specify globs:

purposefile '**' --ignore '**/node_modules/**'

Example output of purposefile for a glob

Note: You can specify multiple --ignore patterns to exclude files from being listed.

If you want to check purposefile before every commit, you can do so with Husky:

{
	"husky": {
		"hooks": {
			"pre-commit": "purposefile" // Or "purposefile && lint-staged" if you use `lint-staged`
		}
	}
}