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 🙏

© 2024 – Pkg Stats / Ryan Hefner

npmignore

v0.3.1

Published

Command line tool for creating or updating a .npmignore file based on .gitignore.

Downloads

80,459

Readme

npmignore NPM version

Command line tool for creating or updating a .npmignore file based on .gitignore.

Usage

Say .gitignore has:

node_modules/
build/

… so that build output is not committed, and you want .npmignore to have:

node_modules/
src/
test/

… so that source files and test files are not published, but build output is.

Automatic usage

On the command line, run npm install --save-dev npmignore.

In your .gitignore, add .npmignore so that the .npmignore file is no longer committed to version control.

In your package.json, add the following JSON to “scripts” and “publishConfig”:

"scripts": {
    …
    "prepack": "npmignore --auto"
    …
},
"publishConfig": {
    …
    "ignore": [
        "!build/",
        "src/",
        "test/"
    ]
    …
}

Whenever you run npm pack or npm publish, an .npmignore file will automatically be created:

node_modules/
build/

# npmignore
!build/
src/
test/

Manual usage

On the command line run:

npx npmignore -i src/,test/,!build/

An .npmignore file will be created, or updated:

node_modules/
build/

# npmignore
!build/
src/
test/

Heads up!

The # npmignore comment is used to ensure that .npmignore reflects the latest changes in your .gitignore file, just by running npmignore in the command line.

_If you want to preserve everything in your .npmignore file, regardless of what is in .gitignore, just add the # npmignore comment at the top of the .npmignore file.

Verification

Run npm pack --dry-run (or npm publish --dry-run) in a modern version of npm to get a printout of the files that will be included in your npm package.

CLI commands

  • --auto: automatic mode. The --ignore, --unignore, keepdest, and --npmignore options are incompatible with this mode.
  • -i|--ignore: comma-separated list of patterns to add to .npmignore
  • -u|--unignore: comma-separated list of patterns to remove from .npmignore. This will not un-ignore patterns in .gitignore.
  • -d|--dest: optionally define a different destination filepath. Good for test driving to see what will be generated in advance.
  • -g|--gitignore: alternate source filepath for .gitignore.
  • -n|--npmignore: alternate source filepath for .npmignore.
  • -k|--keepdest: avoids altering the destination file
  • --commentLines: a comma-separated list of lines of comment text.

API

To use via API, first:

npm install --save npmignore

Then:

var npmignore = require('npmignore');

npmignore(npm, git, options);

Params

  • npm {String|Array}: String from .npmignore or an array of patterns to use.
  • git {String|Array}: String from .gitignore or an array of patterns to use.
  • options {Object}
    • commentLines Array of comment lines. Defaults to:
      [
          'content above this line is automatically generated and modifications may be omitted',
          'see npmjs.com/npmignore for more details.'
      ]
    • ignore Array of patterns to add to the existing patterns from .gitignore
    • unignore Array of patterns to remove from .npmignore. This will not un-ignore patterns in .gitignore
    • keepdest if true, avoids altering the destination file

Tests

Simply clone the repo, npm install, and run npm test

Contributing

Pull requests and stars are always welcome. For bugs and feature requests, please create an issue