diff options
Diffstat (limited to 'deps/npm/html/doc/misc')
| -rw-r--r-- | deps/npm/html/doc/misc/npm-coding-style.html | 2 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-config.html | 60 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-developers.html | 2 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-disputes.html | 168 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-index.html | 4 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-orgs.html | 2 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-registry.html | 22 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-scope.html | 2 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-scripts.html | 30 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/removing-npm.html | 2 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/semver.html | 2 |
11 files changed, 184 insertions, 112 deletions
diff --git a/deps/npm/html/doc/misc/npm-coding-style.html b/deps/npm/html/doc/misc/npm-coding-style.html index 93ab1a0e18..0873b5f82f 100644 --- a/deps/npm/html/doc/misc/npm-coding-style.html +++ b/deps/npm/html/doc/misc/npm-coding-style.html @@ -153,5 +153,5 @@ set to anything."</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-coding-style — npm@3.10.10</p> +<p id="footer">npm-coding-style — npm@4.0.5</p> diff --git a/deps/npm/html/doc/misc/npm-config.html b/deps/npm/html/doc/misc/npm-config.html index 75720461f7..c4dca1bc18 100644 --- a/deps/npm/html/doc/misc/npm-config.html +++ b/deps/npm/html/doc/misc/npm-config.html @@ -24,7 +24,10 @@ interpreted as a configuration parameter. For example, putting configuration parameter to <code>bar</code>. Any environment configurations that are not given a value will be given the value of <code>true</code>. Config values are case-insensitive, so <code>NPM_CONFIG_FOO=bar</code> will work the -same.</p> +same. However, please note that inside <a href="/misc/scripts">npm-scripts</a> +npm will set it's own environment variables and Node will prefer +those lowercase versions over any uppercase ones that you might set. +For details see <a href="https://github.com/npm/npm/issues/14528">this issue</a>.</p> <h3 id="npmrc-files">npmrc Files</h3> <p>The four relevant files are:</p> <ul> @@ -236,8 +239,6 @@ e.g., <code>npm outdated --depth 9999</code></p> <li>Type: Boolean</li> </ul> <p>Install <code>dev-dependencies</code> along with packages.</p> -<p>Note that <code>dev-dependencies</code> are also installed if the <code>npat</code> flag is -set.</p> <h3 id="dry-run">dry-run</h3> <ul> <li>Default: false</li> @@ -431,9 +432,9 @@ version number, if not already set in package.json.</p> <li>Type: Boolean</li> </ul> <p>Whether or not to output JSON data, rather than the normal output.</p> -<p>This feature is currently experimental, and the output data structures -for many commands is either not implemented in JSON yet, or subject to -change. Only the output from <code>npm ls --json</code> is currently valid.</p> +<p>This feature is currently experimental, and the output data structures for many +commands is either not implemented in JSON yet, or subject to change. Only the +output from <code>npm ls --json</code> and <code>npm search --json</code> are currently valid.</p> <h3 id="key">key</h3> <ul> <li>Default: <code>null</code></li> @@ -522,12 +523,6 @@ combination). Passed to the <code>http</code> <code>Agent</code> used to make th <li>Type: semver or false</li> </ul> <p>The node version to use when checking a package's <code>engines</code> map.</p> -<h3 id="npat">npat</h3> -<ul> -<li>Default: false</li> -<li>Type: Boolean</li> -</ul> -<p>Run tests on installation.</p> <h3 id="onload-script">onload-script</h3> <ul> <li>Default: false</li> @@ -563,7 +558,7 @@ process is not aborted.</p> <li>Type: Boolean</li> </ul> <p>Output parseable results from commands that write to -standard output.</p> +standard output. For <code>npm search</code>, this will be tab-separated table format.</p> <h3 id="prefix">prefix</h3> <ul> <li>Default: see <a href="../files/npm-folders.html">npm-folders(5)</a></li> @@ -685,7 +680,7 @@ set to <code>^1.2.3</code> which allows minor upgrades for that package, but aft patch upgrades.</p> <h3 id="scope">scope</h3> <ul> -<li>Default: ""</li> +<li>Default: the scope of the current project, if any, or ""</li> <li>Type: String</li> </ul> <p>Associate an operation with a scope for a scoped registry. Useful when logging @@ -693,27 +688,40 @@ in to a private registry for the first time: <code>npm login --scope=@organization --registry=registry.organization.com</code>, which will cause <code>@organization</code> to be mapped to the registry for future installation of packages specified according to the pattern <code>@organization/package</code>.</p> -<h3 id="searchopts">searchopts</h3> +<h3 id="scripts-prepend-node-path">scripts-prepend-node-path</h3> +<ul> +<li>Default: "warn-only"</li> +<li>Type: Boolean, <code>"auto"</code> or <code>"warn-only"</code></li> +</ul> +<p>If set to <code>true</code>, add the directory in which the current <code>node</code> executable +resides to the <code>PATH</code> environment variable when running scripts, +even if that means that <code>npm</code> will invoke a different <code>node</code> executable than +the one which it is running.</p> +<p>If set to <code>false</code>, never modify <code>PATH</code> with that.</p> +<p>If set to <code>"warn-only"</code>, never modify <code>PATH</code> but print a warning if <code>npm</code> thinks +that you may want to run it with <code>true</code>, e.g. because the <code>node</code> executable +in the <code>PATH</code> is not the one <code>npm</code> was invoked with.</p> +<p>If set to <code>auto</code>, only add that directory to the <code>PATH</code> environment variable +if the <code>node</code> executable with which <code>npm</code> was invoked and the one that is found +first on the <code>PATH</code> are different.</p> +<h3 id="searchexclude">searchexclude</h3> <ul> <li>Default: ""</li> <li>Type: String</li> </ul> -<p>Space-separated options that are always passed to search.</p> -<h3 id="searchexclude">searchexclude</h3> +<p>Space-separated options that limit the results from search.</p> +<h3 id="searchopts">searchopts</h3> <ul> <li>Default: ""</li> <li>Type: String</li> </ul> -<p>Space-separated options that limit the results from search.</p> -<h3 id="searchsort">searchsort</h3> +<p>Space-separated options that are always passed to search.</p> +<h3 id="searchstaleness">searchstaleness</h3> <ul> -<li>Default: "name"</li> -<li>Type: String</li> -<li>Values: "name", "-name", "date", "-date", "description", -"-description", "keywords", "-keywords"</li> +<li>Default: 900 (15 minutes)</li> +<li>Type: Number</li> </ul> -<p>Indication of which field to sort search results by. Prefix with a <code>-</code> -character to indicate reverse sort.</p> +<p>The age of the cache, in seconds, before another registry request is made.</p> <h3 id="shell">shell</h3> <ul> <li>Default: SHELL environment variable, or "bash" on Posix, or "cmd" on @@ -864,5 +872,5 @@ exit successfully.</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-config — npm@3.10.10</p> +<p id="footer">npm-config — npm@4.0.5</p> diff --git a/deps/npm/html/doc/misc/npm-developers.html b/deps/npm/html/doc/misc/npm-developers.html index 2c64e124ce..3b04dffacf 100644 --- a/deps/npm/html/doc/misc/npm-developers.html +++ b/deps/npm/html/doc/misc/npm-developers.html @@ -194,5 +194,5 @@ from a fresh checkout.</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-developers — npm@3.10.10</p> +<p id="footer">npm-developers — npm@4.0.5</p> diff --git a/deps/npm/html/doc/misc/npm-disputes.html b/deps/npm/html/doc/misc/npm-disputes.html index 69a49b6e74..3db7ef27db 100644 --- a/deps/npm/html/doc/misc/npm-disputes.html +++ b/deps/npm/html/doc/misc/npm-disputes.html @@ -10,91 +10,113 @@ <div id="wrapper"> <h1><a href="../misc/npm-disputes.html">npm-disputes</a></h1> <p>Handling Module Name Disputes</p> -<h2 id="synopsis">SYNOPSIS</h2> +<p>This document describes the steps that you should take to resolve module name +disputes with other npm publishers. It also describes special steps you should +take about names you think infringe your trademarks.</p> +<p>This document is a clarification of the acceptable behavior outlined in the +<a href="https://www.npmjs.com/policies/conduct">npm Code of Conduct</a>, and nothing in +this document should be interpreted to contradict any aspect of the npm Code of +Conduct.</p> +<h2 id="tl-dr">TL;DR</h2> <ol> <li>Get the author email with <code>npm owner ls <pkgname></code></li> -<li>Email the author, CC <a href="mailto:support@npmjs.com">support@npmjs.com</a></li> +<li>Email the author, CC <a href="mailto:support@npmjs.com">support@npmjs.com</a></li> <li>After a few weeks, if there's no resolution, we'll sort it out.</li> </ol> <p>Don't squat on package names. Publish code or move out of the way.</p> <h2 id="description">DESCRIPTION</h2> -<p>There sometimes arise cases where a user publishes a module, and then -later, some other user wants to use that name. Here are some common -ways that happens (each of these is based on actual events.)</p> +<p>There sometimes arise cases where a user publishes a module, and then later, +some other user wants to use that name. Here are some common ways that happens +(each of these is based on actual events.)</p> <ol> -<li>Joe writes a JavaScript module <code>foo</code>, which is not node-specific. -Joe doesn't use node at all. Bob wants to use <code>foo</code> in node, so he -wraps it in an npm module. Some time later, Joe starts using node, -and wants to take over management of his program.</li> -<li>Bob writes an npm module <code>foo</code>, and publishes it. Perhaps much -later, Joe finds a bug in <code>foo</code>, and fixes it. He sends a pull -request to Bob, but Bob doesn't have the time to deal with it, -because he has a new job and a new baby and is focused on his new -erlang project, and kind of not involved with node any more. Joe -would like to publish a new <code>foo</code>, but can't, because the name is -taken.</li> -<li>Bob writes a 10-line flow-control library, and calls it <code>foo</code>, and -publishes it to the npm registry. Being a simple little thing, it -never really has to be updated. Joe works for Foo Inc, the makers -of the critically acclaimed and widely-marketed <code>foo</code> JavaScript -toolkit framework. They publish it to npm as <code>foojs</code>, but people are -routinely confused when <code>npm install foo</code> is some different thing.</li> -<li>Bob writes a parser for the widely-known <code>foo</code> file format, because -he needs it for work. Then, he gets a new job, and never updates the -prototype. Later on, Joe writes a much more complete <code>foo</code> parser, -but can't publish, because Bob's <code>foo</code> is in the way.</li> -</ol> -<p>The validity of Joe's claim in each situation can be debated. However, -Joe's appropriate course of action in each case is the same.</p> -<ol> -<li><code>npm owner ls foo</code>. This will tell Joe the email address of the -owner (Bob).</li> -<li>Joe emails Bob, explaining the situation <strong>as respectfully as -possible</strong>, and what he would like to do with the module name. He -adds the npm support staff <a href="mailto:support@npmjs.com">support@npmjs.com</a> to the CC list of -the email. Mention in the email that Bob can run <code>npm owner add -joe foo</code> to add Joe as an owner of the <code>foo</code> package.</li> -<li>After a reasonable amount of time, if Bob has not responded, or if -Bob and Joe can't come to any sort of resolution, email support -<a href="mailto:support@npmjs.com">support@npmjs.com</a> and we'll sort it out. ("Reasonable" is -usually at least 4 weeks, but extra time is allowed around common -holidays.)</li> +<li>Alice writes a JavaScript module <code>foo</code>, which is not node-specific. Alice +doesn't use node at all. Yusuf wants to use <code>foo</code> in node, so he wraps it in +an npm module. Some time later, Alice starts using node, and wants to take +over management of her program.</li> +<li>Yusuf writes an npm module <code>foo</code>, and publishes it. Perhaps much later, Alice +finds a bug in <code>foo</code>, and fixes it. She sends a pull request to Yusuf, but +Yusuf doesn't have the time to deal with it, because he has a new job and a +new baby and is focused on his new Erlang project, and kind of not involved +with node any more. Alice would like to publish a new <code>foo</code>, but can't, +because the name is taken.</li> +<li>Yusuf writes a 10-line flow-control library, and calls it <code>foo</code>, and +publishes it to the npm registry. Being a simple little thing, it never +really has to be updated. Alice works for Foo Inc, the makers of the +critically acclaimed and widely-marketed <code>foo</code> JavaScript toolkit framework. +They publish it to npm as <code>foojs</code>, but people are routinely confused when +<code>npm install</code>foo`` is some different thing.</li> +<li><p>Yusuf writes a parser for the widely-known <code>foo</code> file format, because he +needs it for work. Then, he gets a new job, and never updates the prototype. +Later on, Alice writes a much more complete <code>foo</code> parser, but can't publish, +because Yusuf's <code>foo</code> is in the way.</p> +</li> +<li><p><code>npm owner ls foo</code>. This will tell Alice the email address of the owner +(Yusuf).</p> +</li> +<li>Alice emails Yusuf, explaining the situation <strong>as respectfully as possible</strong>, +and what she would like to do with the module name. She adds the npm support +staff <a href="mailto:support@npmjs.com">support@npmjs.com</a> to the CC list of the email. Mention in the email +that Yusuf can run npm owner <code>add alice foo</code> to add Alice as an owner of the +foo package.</li> +<li>After a reasonable amount of time, if Yusuf has not responded, or if Yusuf +and Alice can't come to any sort of resolution, email support +<a href="mailto:support@npmjs.com">support@npmjs.com</a> and we'll sort it out. ("Reasonable" is usually at least +4 weeks.)</li> </ol> <h2 id="reasoning">REASONING</h2> -<p>In almost every case so far, the parties involved have been able to reach -an amicable resolution without any major intervention. Most people -really do want to be reasonable, and are probably not even aware that -they're in your way.</p> -<p>Module ecosystems are most vibrant and powerful when they are as -self-directed as possible. If an admin one day deletes something you -had worked on, then that is going to make most people quite upset, -regardless of the justification. When humans solve their problems by -talking to other humans with respect, everyone has the chance to end up -feeling good about the interaction.</p> +<p>In almost every case so far, the parties involved have been able to reach an +amicable resolution without any major intervention. Most people really do want +to be reasonable, and are probably not even aware that they're in your way.</p> +<p>Module ecosystems are most vibrant and powerful when they are as self-directed +as possible. If an admin one day deletes something you had worked on, then that +is going to make most people quite upset, regardless of the justification. When +humans solve their problems by talking to other humans with respect, everyone +has the chance to end up feeling good about the interaction.</p> <h2 id="exceptions">EXCEPTIONS</h2> -<p>Some things are not allowed, and will be removed without discussion if -they are brought to the attention of the npm registry admins, including -but not limited to:</p> +<p>Some things are not allowed, and will be removed without discussion if they are +brought to the attention of the npm registry admins, including but not limited +to:</p> <ol> -<li>Malware (that is, a package designed to exploit or harm the machine on -which it is installed).</li> -<li>Violations of copyright or licenses (for example, cloning an -MIT-licensed program, and then removing or changing the copyright and -license statement).</li> +<li>Malware (that is, a package designed to exploit or harm the machine on which +it is installed).</li> +<li>Violations of copyright or licenses (for example, cloning an MIT-licensed +program, and then removing or changing the copyright and license statement).</li> <li>Illegal content.</li> -<li>"Squatting" on a package name that you <em>plan</em> to use, but aren't -actually using. Sorry, I don't care how great the name is, or how -perfect a fit it is for the thing that someday might happen. If -someone wants to use it today, and you're just taking up space with -an empty tarball, you're going to be evicted.</li> -<li>Putting empty packages in the registry. Packages must have SOME -functionality. It can be silly, but it can't be <em>nothing</em>. (See -also: squatting.)</li> -<li>Doing weird things with the registry, like using it as your own -personal application database or otherwise putting non-packagey -things into it.</li> +<li>"Squatting" on a package name that you plan to use, but aren't actually +using. Sorry, I don't care how great the name is, or how perfect a fit it is +for the thing that someday might happen. If someone wants to use it today, +and you're just taking up space with an empty tarball, you're going to be +evicted.</li> +<li>Putting empty packages in the registry. Packages must have SOME +functionality. It can be silly, but it can't be nothing. (See also: +squatting.)</li> +<li>Doing weird things with the registry, like using it as your own personal +application database or otherwise putting non-packagey things into it.</li> +<li>Other things forbidden by the npm +<a href="https://www.npmjs.com/policies/conduct">Code of Conduct</a> such as hateful +language, pornographic content, or harassment.</li> </ol> -<p>If you see bad behavior like this, please report it right away.</p> +<p>If you see bad behavior like this, please report it to <a href="mailto:abuse@npmjs.com">abuse@npmjs.com</a> right +away. <strong>You are never expected to resolve abusive behavior on your own. We are +here to help.</strong></p> +<h2 id="trademarks">TRADEMARKS</h2> +<p>If you think another npm publisher is infringing your trademark, such as by +using a confusingly similar package name, email <a href="mailto:abuse@npmjs.com">abuse@npmjs.com</a> with a link to +the package or user account on <a href="https://npmjs.com">https://npmjs.com</a>. Attach a +copy of your trademark registration certificate.</p> +<p>If we see that the package's publisher is intentionally misleading others by +misusing your registered mark without permission, we will transfer the package +name to you. Otherwise, we will contact the package publisher and ask them to +clear up any confusion with changes to their package's <code><a href="../../doc/README.html">README</a></code> file or +metadata.</p> +<h2 id="changes">CHANGES</h2> +<p>This is a living document and may be updated from time to time. Please refer to +the <a href="https://github.com/npm/npm/commits/master/doc/misc/npm-disputes.md">git history for this document</a> +to view the changes.</p> +<h2 id="license">LICENSE</h2> +<p>Copyright (C) npm, Inc., All rights reserved</p> +<p>This document may be reused under a Creative Commons Attribution-ShareAlike +License.</p> <h2 id="see-also">SEE ALSO</h2> <ul> <li><a href="../misc/npm-registry.html">npm-registry(7)</a></li> @@ -112,5 +134,5 @@ things into it.</li> <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-disputes — npm@3.10.10</p> +<p id="footer">npm-disputes — npm@4.0.5</p> diff --git a/deps/npm/html/doc/misc/npm-index.html b/deps/npm/html/doc/misc/npm-index.html index 702e543023..4e590dabe7 100644 --- a/deps/npm/html/doc/misc/npm-index.html +++ b/deps/npm/html/doc/misc/npm-index.html @@ -98,8 +98,6 @@ <p>Start a package</p> <h3 id="npm-stop-1-"><a href="../cli/npm-stop.html">npm-stop(1)</a></h3> <p>Stop a package</p> -<h3 id="npm-tag-1-"><a href="../cli/npm-tag.html">npm-tag(1)</a></h3> -<p>Tag a published version</p> <h3 id="npm-team-1-"><a href="../cli/npm-team.html">npm-team(1)</a></h3> <p>Manage organization teams and team memberships</p> <h3 id="npm-test-1-"><a href="../cli/npm-test.html">npm-test(1)</a></h3> @@ -162,5 +160,5 @@ <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-index — npm@3.10.10</p> +<p id="footer">npm-index — npm@4.0.5</p> diff --git a/deps/npm/html/doc/misc/npm-orgs.html b/deps/npm/html/doc/misc/npm-orgs.html index 7d5a7cba38..92aa4257e8 100644 --- a/deps/npm/html/doc/misc/npm-orgs.html +++ b/deps/npm/html/doc/misc/npm-orgs.html @@ -86,5 +86,5 @@ <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-orgs — npm@3.10.10</p> +<p id="footer">npm-orgs — npm@4.0.5</p> diff --git a/deps/npm/html/doc/misc/npm-registry.html b/deps/npm/html/doc/misc/npm-registry.html index b36cfa5bbe..a780c98a45 100644 --- a/deps/npm/html/doc/misc/npm-registry.html +++ b/deps/npm/html/doc/misc/npm-registry.html @@ -25,6 +25,26 @@ available at <a href="https://github.com/npm/npm-registry-couchapp">https://gith <code><a href="../misc/npm-scope.html">npm-scope(7)</a></code>). If no scope is specified, the default registry is used, which is supplied by the <code>registry</code> config parameter. See <code><a href="../cli/npm-config.html">npm-config(1)</a></code>, <code><a href="../files/npmrc.html">npmrc(5)</a></code>, and <code><a href="../misc/npm-config.html">npm-config(7)</a></code> for more on managing npm's configuration.</p> +<h2 id="does-npm-send-any-information-about-me-back-to-the-registry-">Does npm send any information about me back to the registry?</h2> +<p>Yes.</p> +<p>When making requests of the registry npm adds two headers with information +about your environment:</p> +<ul> +<li><code>Npm-Scope</code> – If your project is scoped, this header will contain its +scope. In the future npm hopes to build registry features that use this +information to allow you to customize your experience for your +organization.</li> +<li><code>Npm-In-CI</code> – Set to "true" if npm believes this install is running in a +continous integration environment, "false" otherwise. This is detected by +looking for the following environment variables: <code>CI</code>, <code>TDDIUM</code>, +<code>JENKINS_URL</code>, <code>bamboo.buildKey</code>. If you'd like to learn more you may find +the <a href="https://github.com/npm/npm-registry-client/pull/129">original PR</a> +interesting. +This is used to gather better metrics on how npm is used by humans, versus +build farms.</li> +</ul> +<p>The npm registry does not to correlate the information in these headers with +any authenticated accounts that may be used in the same requests.</p> <h2 id="can-i-run-my-own-private-registry-">Can I run my own private registry?</h2> <p>Yes!</p> <p>The easiest way is to replicate the couch database, and use the same (or @@ -70,5 +90,5 @@ effectively implement the entire CouchDB API anyway.</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-registry — npm@3.10.10</p> +<p id="footer">npm-registry — npm@4.0.5</p> diff --git a/deps/npm/html/doc/misc/npm-scope.html b/deps/npm/html/doc/misc/npm-scope.html index aed4efe7d1..7295c81fd8 100644 --- a/deps/npm/html/doc/misc/npm-scope.html +++ b/deps/npm/html/doc/misc/npm-scope.html @@ -94,5 +94,5 @@ that registry instead.</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-scope — npm@3.10.10</p> +<p id="footer">npm-scope — npm@4.0.5</p> diff --git a/deps/npm/html/doc/misc/npm-scripts.html b/deps/npm/html/doc/misc/npm-scripts.html index 172a6cd748..c140ea2152 100644 --- a/deps/npm/html/doc/misc/npm-scripts.html +++ b/deps/npm/html/doc/misc/npm-scripts.html @@ -16,7 +16,13 @@ following scripts:</p> <ul> <li>prepublish: Run BEFORE the package is published. (Also run on local <code>npm -install</code> without any arguments.)</li> +install</code> without any arguments. See below.)</li> +<li>prepare: +Run both BEFORE the package is published, and on local <code>npm +install</code> without any arguments. (See below.) This is run +AFTER <code>prepublish</code>, but BEFORE <code>prepublishOnly</code>.</li> +<li>prepublishOnly: +Run BEFORE the package is published. (See below.)</li> <li>publish, postpublish: Run AFTER the package is published.</li> <li>preinstall: @@ -50,7 +56,25 @@ run-script <stage></code>. <em>Pre</em> and <em>post</em> commands with ma names will be run for those as well (e.g. <code>premyscript</code>, <code>myscript</code>, <code>postmyscript</code>). Scripts from dependencies can be run with `npm explore</p> <p><pkg> -- npm run <stage>`.</p> -<h2 id="common-uses">COMMON USES</h2> +<h2 id="prepublish-and-prepare">PREPUBLISH AND PREPARE</h2> +<h3 id="deprecation-note">DEPRECATION NOTE</h3> +<p>Since <code>npm@1.1.71</code>, the npm CLI has run the <code>prepublish</code> script for both <code>npm +publish</code> and <code>npm install</code>, because it's a convenient way to prepare a package +for use (some common use cases are described in the section below). It has +also turned out to be, in practice, <a href="https://github.com/npm/npm/issues/10074">very +confusing</a>. As of <code>npm@4.0.0</code>, a new +event has been introduced, <code>prepare</code>, that preserves this existing behavior. A +<em>new</em> event, <code>prepublishOnly</code> has been added as a transitional strategy to +allow users to avoid the confusing behavior of existing npm versions and only +run on <code>npm publish</code> (for instance, running the tests one last time to ensure +they're in good shape).</p> +<p><strong>IMPORTANT:</strong> As of <code>npm@5</code>, <code>prepublish</code> will <em>only</em> be run for <code>npm +publish</code>. This will make its behavior identical to <code>prepublishOnly</code>, so +<code>npm@6</code> or later may drop support for the use of <code>prepublishOnly</code>, and then +maybe we can all forget this embarrassing thing ever happened.</p> +<p>See <a href="https://github.com/npm/npm/issues/10074">https://github.com/npm/npm/issues/10074</a> for a much lengthier +justification, with further reading, for this change.</p> +<h3 id="use-cases">USE CASES</h3> <p>If you need to perform operations on your package before it is used, in a way that is not dependent on the operating system or architecture of the target system, use a <code>prepublish</code> script. This includes @@ -213,5 +237,5 @@ scripts is for compilation which must be done on the target architecture.</li> <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-scripts — npm@3.10.10</p> +<p id="footer">npm-scripts — npm@4.0.5</p> diff --git a/deps/npm/html/doc/misc/removing-npm.html b/deps/npm/html/doc/misc/removing-npm.html index 6b2f30a72b..63d0648844 100644 --- a/deps/npm/html/doc/misc/removing-npm.html +++ b/deps/npm/html/doc/misc/removing-npm.html @@ -57,5 +57,5 @@ modules. To track those down, you can do the following:</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">removing-npm — npm@3.10.10</p> +<p id="footer">removing-npm — npm@4.0.5</p> diff --git a/deps/npm/html/doc/misc/semver.html b/deps/npm/html/doc/misc/semver.html index 7e053f6228..2ae0288f99 100644 --- a/deps/npm/html/doc/misc/semver.html +++ b/deps/npm/html/doc/misc/semver.html @@ -325,5 +325,5 @@ range, use the <code>satisfies(version, range)</code> function.</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">semver — npm@3.10.10</p> +<p id="footer">semver — npm@4.0.5</p> |