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

unignored

v1.0.6

Published

Check what files in an npm project will be published

Readme

Unignored

Check what files in an npm project will be published

Install

npm install unignored

Use

var unignored = require('unignored')
unignored('./', function(err, files) {
  console.log(files)
})

Simply require unignored and pass it a path to the npm project you'd like to check. Files will be an array of file paths (relative to the path you passed in) that will be included when you run npm publish.

CLI

You can install the module globally and use it as a cli as well:

Usage: unignored [options]

Options:
  -p, --path     path to module (relative)    [default: "./"]
  -h, --help     Show help
  -v, --version  Show version number

Why

Since creating this tool, I've found a few other modules that accomplish this same task like irish-pub and pkgfiles. They both include more features and are recommended if unignored doesn't work out for you.

NPM is very smart about which files are included and which are ignored by default. This is highly configurable with .gitignore, .npmignore, and the files key in package.json. Because these rules are slightly complex, it can be helpful to see what files all consumers of your module will have to download when they install it.

About NPM Ignore

This section of the manual explains this in pretty good detail.

Essentially, if there is no .npmignore, the .gitignore will be used. That means anything that you are ignoring from source control won't be part of your module when people npm install it.

If there is a files field in package.json, then that will dictate what files are included in the version.

If you have both files and .npmignore and they conflict, .npmignore will override the file and it will still be ignored.

Contribute

Contributions are welcome! This project uses the standard style, so you should use it too! npm test will automatically make sure the code is written to the standard. If the tests pass, you are good to go!