diff options
| author | Kat Marchán <kzm@sykosomatic.org> | 2015-07-31 17:08:03 -0700 |
|---|---|---|
| committer | Jeremiah Senkpiel <fishrock123@rocketmail.com> | 2015-08-01 09:45:44 -0700 |
| commit | bf63266460f79d1e8ca71fbfd5898211c438ce80 (patch) | |
| tree | 618e302343a5215270c6416420a374dd1ba9feb3 /deps/npm/html/doc/files/npm-json.html | |
| parent | d5ab92bcc1f0ddf7ea87a8322824a688dfd43bf5 (diff) | |
| download | node-new-bf63266460f79d1e8ca71fbfd5898211c438ce80.tar.gz | |
deps: upgrade to npm 2.13.3
PR-URL: https://github.com/nodejs/io.js/pull/2284
Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com>
Diffstat (limited to 'deps/npm/html/doc/files/npm-json.html')
| -rw-r--r-- | deps/npm/html/doc/files/npm-json.html | 34 |
1 files changed, 27 insertions, 7 deletions
diff --git a/deps/npm/html/doc/files/npm-json.html b/deps/npm/html/doc/files/npm-json.html index 1b7cd7a8de..2fcc8a78ab 100644 --- a/deps/npm/html/doc/files/npm-json.html +++ b/deps/npm/html/doc/files/npm-json.html @@ -140,6 +140,26 @@ inside that folder. (Unless they would be ignored by another rule.)</p> 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".</p> +<p>Certain files are always included, regardless of settings:</p> +<ul> +<li><code>package.json</code></li> +<li><code><a href="../../doc/README.html"><a href="../../doc/README.html">README</a></a></code> (and its variants)</li> +<li><code>CHANGELOG</code> (and its variants)</li> +<li><code>LICENSE</code> / <code>LICENCE</code></li> +</ul> +<p>Conversely, some files are always ignored:</p> +<ul> +<li><code>.git</code></li> +<li><code>CVS</code></li> +<li><code>.svn</code></li> +<li><code>.hg</code></li> +<li><code>.lock-wscript</code></li> +<li><code>.wafpickle-N</code></li> +<li><code>*.swp</code></li> +<li><code>.DS_Store</code></li> +<li><code>._*</code></li> +<li><code>npm-debug.log</code></li> +</ul> <h2 id="main">main</h2> <p>The main field is a module ID that is the primary entry point to your program. That is, if your package is named <code>foo</code>, and a user installs it, and then does @@ -494,12 +514,12 @@ specific registry (for example, an internal registry), then use the <code>publishConfig</code> dictionary described below to override the <code>registry</code> config param at publish-time.</p> <h2 id="publishconfig">publishConfig</h2> -<p>This is a set of config values that will be used at publish-time. It's -especially handy if you want to set the tag or registry, so that you can -ensure that a given package is not tagged with "latest" or published to -the global public registry by default.</p> -<p>Any config values can be overridden, but of course only "tag" and -"registry" probably matter for the purposes of publishing.</p> +<p>This is a set of config values that will be used at publish-time. It's +especially handy if you want to set the tag, registry or access, so that +you can ensure that a given package is not tagged with "latest", published +to the global public registry or that a scoped module is private by default.</p> +<p>Any config values can be overridden, but of course only "tag", "registry" and +"access" probably matter for the purposes of publishing.</p> <p>See <code><a href="../misc/npm-config.html"><a href="../misc/npm-config.html">npm-config(7)</a></a></code> to see the list of config options that can be overridden.</p> <h2 id="default-values">DEFAULT VALUES</h2> @@ -545,5 +565,5 @@ ignored.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-json — npm@2.13.2</p> +<p id="footer">npm-json — npm@2.13.3</p> |