Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP


Point out npm's usage of .gitignore on the npm-json(1) page #2363

wants to merge 1 commit into from

4 participants


This calls out a potentially confusing behavior. See #1862.


Looks good to me.


We already have this information in both npm help config and npm help developers. Personally I'd prefer to avoid repeating everything everywhere.


This is pretty well documented in npm help developers.

@luk- luk- closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Apr 12, 2012
  1. @cespare
This page is out of date. Refresh to see the latest.
Showing with 2 additions and 1 deletion.
  1. +2 −1  doc/cli/
3  doc/cli/
@@ -140,7 +140,8 @@ inside that folder. (Unless they would be ignored by another rule.)
You can also provide a ".npmignore" file in the root of your package,
which will keep files from being included, even if they would be picked
up by the files array. The ".npmignore" file works just like a
+".gitignore", and npm will use ".gitignore" if no ".npmignore" file exists. See
+`npm-developers(1)` for more information.
## main
Something went wrong with that request. Please try again.