diff options
Diffstat (limited to 'deps/npm/html/doc/misc')
| -rw-r--r-- | deps/npm/html/doc/misc/npm-coding-style.html | 26 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-config.html | 45 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-developers.html | 20 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-disputes.html | 16 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-index.html | 2 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-orgs.html | 29 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-registry.html | 6 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-scope.html | 20 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-scripts.html | 29 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/removing-npm.html | 17 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/semver.html | 35 |
11 files changed, 102 insertions, 143 deletions
diff --git a/deps/npm/html/doc/misc/npm-coding-style.html b/deps/npm/html/doc/misc/npm-coding-style.html index 204556e25a..e8133c1794 100644 --- a/deps/npm/html/doc/misc/npm-coding-style.html +++ b/deps/npm/html/doc/misc/npm-coding-style.html @@ -29,21 +29,17 @@ statements onto multiple lines.</p> <p>Curly braces belong on the same line as the thing that necessitates them.</p> <p>Bad:</p> <pre><code>function () -{ -</code></pre><p>Good:</p> -<pre><code>function () { -</code></pre><p>If a block needs to wrap to the next line, use a curly brace. Don't +{</code></pre><p>Good:</p> +<pre><code>function () {</code></pre><p>If a block needs to wrap to the next line, use a curly brace. Don't use it if it doesn't.</p> <p>Bad:</p> <pre><code>if (foo) { bar() } while (foo) - bar() -</code></pre><p>Good:</p> + bar()</code></pre><p>Good:</p> <pre><code>if (foo) bar() while (foo) { bar() -} -</code></pre><h2 id="semicolons">Semicolons</h2> +}</code></pre><h2 id="semicolons">Semicolons</h2> <p>Don't use them except in four situations:</p> <ul> <li><code>for (;;)</code> loops. They're actually required.</li> @@ -64,8 +60,7 @@ for (var i = 0; i < 10; i ++) { default: throw new Error('unknown state') } end() -} -</code></pre><p>Note that starting lines with <code>-</code> and <code>+</code> also should be prefixed +}</code></pre><p>Note that starting lines with <code>-</code> and <code>+</code> also should be prefixed with a semicolon, but this is much less common.</p> <h2 id="comma-first">Comma First</h2> <p>If there is a list of things separated by commas, and it wraps @@ -82,15 +77,12 @@ final token in the list on a line by itself. For example:</p> , a = 1 , b = 'abc' , etc - , somethingElse -</code></pre><h2 id="quotes">Quotes</h2> + , somethingElse</code></pre><h2 id="quotes">Quotes</h2> <p>Use single quotes for strings except to avoid escaping.</p> <p>Bad:</p> -<pre><code>var notOk = "Just double quotes" -</code></pre><p>Good:</p> +<pre><code>var notOk = "Just double quotes"</code></pre><p>Good:</p> <pre><code>var ok = 'String contains "double" quotes' -var alsoOk = "String contains 'single' quotes or apostrophe" -</code></pre><h2 id="whitespace">Whitespace</h2> +var alsoOk = "String contains 'single' quotes or apostrophe"</code></pre><h2 id="whitespace">Whitespace</h2> <p>Put a single space in front of <code>(</code> for anything other than a function call. Also use a single space wherever it makes things more readable.</p> <p>Don't leave trailing whitespace at the end of lines. Don't indent empty @@ -153,5 +145,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@6.1.0</p> +<p id="footer">npm-coding-style — npm@6.2.0</p> diff --git a/deps/npm/html/doc/misc/npm-config.html b/deps/npm/html/doc/misc/npm-config.html index 0abd19a970..fcfbb71f3c 100644 --- a/deps/npm/html/doc/misc/npm-config.html +++ b/deps/npm/html/doc/misc/npm-config.html @@ -82,27 +82,22 @@ configuration parameter, then it is expanded to that configuration parameter. For example:</p> <pre><code>npm ls --par # same as: -npm ls --parseable -</code></pre><p>If multiple single-character shorthands are strung together, and the +npm ls --parseable</code></pre><p>If multiple single-character shorthands are strung together, and the resulting combination is unambiguously not some other configuration param, then it is expanded to its various component pieces. For example:</p> <pre><code>npm ls -gpld # same as: -npm ls --global --parseable --long --loglevel info -</code></pre><h2 id="per-package-config-settings">Per-Package Config Settings</h2> +npm ls --global --parseable --long --loglevel info</code></pre><h2 id="per-package-config-settings">Per-Package Config Settings</h2> <p>When running scripts (see <code><a href="../misc/npm-scripts.html">npm-scripts(7)</a></code>) the package.json "config" keys are overwritten in the environment if there is a config param of <code><name>[@<version>]:<key></code>. For example, if the package.json has this:</p> <pre><code>{ "name" : "foo" , "config" : { "port" : "8080" } -, "scripts" : { "start" : "node server.js" } } -</code></pre><p>and the server.js is this:</p> -<pre><code>http.createServer(...).listen(process.env.npm_package_config_port) -</code></pre><p>then the user could change the behavior by doing:</p> -<pre><code>npm config set foo:port 80 -</code></pre><p>See <a href="../files/package.json.html">package.json(5)</a> for more information.</p> +, "scripts" : { "start" : "node server.js" } }</code></pre><p>and the server.js is this:</p> +<pre><code>http.createServer(...).listen(process.env.npm_package_config_port)</code></pre><p>then the user could change the behavior by doing:</p> +<pre><code>npm config set foo:port 80</code></pre><p>See <a href="../files/package.json.html">package.json(5)</a> for more information.</p> <h2 id="config-settings">Config Settings</h2> <h3 id="access">access</h3> <ul> @@ -172,13 +167,11 @@ ostensibly Unix systems.</p> <p>The Certificate Authority signing certificate that is trusted for SSL connections to the registry. Values should be in PEM format (Windows calls it "Base-64 encoded X.509 (.CER)") with newlines replaced by the string "\n". For example:</p> -<pre><code>ca="-----BEGIN CERTIFICATE-----\nXXXX\nXXXX\n-----END CERTIFICATE-----" -</code></pre><p>Set to <code>null</code> to only allow "known" registrars, or to a specific CA cert +<pre><code>ca="-----BEGIN CERTIFICATE-----\nXXXX\nXXXX\n-----END CERTIFICATE-----"</code></pre><p>Set to <code>null</code> to only allow "known" registrars, or to a specific CA cert to trust only that specific signing authority.</p> <p>Multiple CAs can be trusted by specifying an array of certificates:</p> <pre><code>ca[]="..." -ca[]="..." -</code></pre><p>See also the <code>strict-ssl</code> config.</p> +ca[]="..."</code></pre><p>See also the <code>strict-ssl</code> config.</p> <h3 id="cafile">cafile</h3> <ul> <li>Default: <code>null</code></li> @@ -232,8 +225,7 @@ well as for the CA information to be stored in a file on disk.</p> </ul> <p>A client certificate to pass when accessing the registry. Values should be in PEM format (Windows calls it "Base-64 encoded X.509 (.CER)") with newlines replaced by the string "\n". For example:</p> -<pre><code>cert="-----BEGIN CERTIFICATE-----\nXXXX\nXXXX\n-----END CERTIFICATE-----" -</code></pre><p>It is <em>not</em> the path to a certificate file (and there is no "certfile" option).</p> +<pre><code>cert="-----BEGIN CERTIFICATE-----\nXXXX\nXXXX\n-----END CERTIFICATE-----"</code></pre><p>It is <em>not</em> the path to a certificate file (and there is no "certfile" option).</p> <h3 id="cidr">cidr</h3> <ul> <li>Default: <code>null</code></li> @@ -487,8 +479,7 @@ output from <code>npm ls --json</code> and <code>npm search --json</code> are cu </ul> <p>A client key to pass when accessing the registry. Values should be in PEM format with newlines replaced by the string "\n". For example:</p> -<pre><code>key="-----BEGIN PRIVATE KEY-----\nXXXX\nXXXX\n-----END PRIVATE KEY-----" -</code></pre><p>It is <em>not</em> the path to a key file (and there is no "keyfile" option).</p> +<pre><code>key="-----BEGIN PRIVATE KEY-----\nXXXX\nXXXX\n-----END PRIVATE KEY-----"</code></pre><p>It is <em>not</em> the path to a key file (and there is no "keyfile" option).</p> <h3 id="legacy-bundling">legacy-bundling</h3> <ul> <li>Default: false</li> @@ -884,6 +875,15 @@ Windows</li> <p>If set to false, then ignore <code>npm-shrinkwrap.json</code> files when installing. This will also prevent <em>writing</em> <code>npm-shrinkwrap.json</code> if <code>save</code> is true.</p> <p>This option is an alias for <code>--package-lock</code>.</p> +<h3 id="sign-git-commit">sign-git-commit</h3> +<ul> +<li>Default: false</li> +<li>Type: Boolean</li> +</ul> +<p>If set to true, then the <code>npm version</code> command will commit the new package +version using <code>-S</code> to add a signature.</p> +<p>Note that git requires you to have set up GPG keys in your git configs +for this to work properly.</p> <h3 id="sign-git-tag">sign-git-tag</h3> <ul> <li>Default: false</li> @@ -966,6 +966,13 @@ false, it uses ascii characters to draw trees.</p> <p>Set to true to suppress the UID/GID switching when running package scripts. If set explicitly to false, then installing as a non-root user will fail.</p> +<h3 id="update-notifier">update-notifier</h3> +<ul> +<li>Default: true</li> +<li>Type: Boolean</li> +</ul> +<p>Set to false to suppress the update notification when using an older +version of npm than the latest.</p> <h3 id="usage">usage</h3> <ul> <li>Default: false</li> @@ -1043,5 +1050,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@6.1.0</p> +<p id="footer">npm-config — npm@6.2.0</p> diff --git a/deps/npm/html/doc/misc/npm-developers.html b/deps/npm/html/doc/misc/npm-developers.html index 526bcc6d34..961bf22c41 100644 --- a/deps/npm/html/doc/misc/npm-developers.html +++ b/deps/npm/html/doc/misc/npm-developers.html @@ -39,8 +39,7 @@ after packing it up into a tarball (b).</p> <pre><code>git://github.com/user/project.git#commit-ish git+ssh://user@hostname:project.git#commit-ish git+http://user@hostname/project/blah.git#commit-ish -git+https://user@hostname/project/blah.git#commit-ish -</code></pre><p>The <code>commit-ish</code> can be any tag, sha, or branch which can be supplied as +git+https://user@hostname/project/blah.git#commit-ish</code></pre><p>The <code>commit-ish</code> can be any tag, sha, or branch which can be supplied as an argument to <code>git checkout</code>. The default is <code>master</code>.</p> <h2 id="the-package-json-file">The package.json File</h2> <p>You need to have a <code>package.json</code> file in the root of your project to do @@ -154,26 +153,21 @@ problems trying to publish it. Or, worse yet, you'll be able to publish it, but you'll be publishing a broken or pointless package. So don't do that.</p> <p>In the root of your package, do this:</p> -<pre><code>npm install . -g -</code></pre><p>That'll show you that it's working. If you'd rather just create a symlink +<pre><code>npm install . -g</code></pre><p>That'll show you that it's working. If you'd rather just create a symlink package that points to your working directory, then do this:</p> -<pre><code>npm link -</code></pre><p>Use <code>npm ls -g</code> to see if it's there.</p> +<pre><code>npm link</code></pre><p>Use <code>npm ls -g</code> to see if it's there.</p> <p>To test a local install, go into some other folder, and then do:</p> <pre><code>cd ../some-other-folder -npm install ../my-package -</code></pre><p>to install it locally into the node_modules folder in that other place.</p> +npm install ../my-package</code></pre><p>to install it locally into the node_modules folder in that other place.</p> <p>Then go into the node-repl, and try using require("my-thing") to bring in your module's main module.</p> <h2 id="create-a-user-account">Create a User Account</h2> <p>Create a user with the adduser command. It works like this:</p> -<pre><code>npm adduser -</code></pre><p>and then follow the prompts.</p> +<pre><code>npm adduser</code></pre><p>and then follow the prompts.</p> <p>This is documented better in <a href="../cli/npm-adduser.html">npm-adduser(1)</a>.</p> <h2 id="publish-your-package">Publish your package</h2> <p>This part's easy. In the root of your folder, do this:</p> -<pre><code>npm publish -</code></pre><p>You can give publish a url to a tarball, or a filename of a tarball, +<pre><code>npm publish</code></pre><p>You can give publish a url to a tarball, or a filename of a tarball, or a path to a folder.</p> <p>Note that pretty much <strong>everything in that folder will be exposed</strong> by default. So, if you have secret stuff in there, use a @@ -204,5 +198,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@6.1.0</p> +<p id="footer">npm-developers — npm@6.2.0</p> diff --git a/deps/npm/html/doc/misc/npm-disputes.html b/deps/npm/html/doc/misc/npm-disputes.html index 543a601979..dccfe0394b 100644 --- a/deps/npm/html/doc/misc/npm-disputes.html +++ b/deps/npm/html/doc/misc/npm-disputes.html @@ -20,7 +20,7 @@ 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> @@ -44,7 +44,7 @@ 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<code></code> is some different thing.</li> +<code>npm install foo</code> 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, @@ -55,12 +55,12 @@ because Yusuf's <code>foo</code> is in the way.</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 +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 +<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> @@ -96,12 +96,12 @@ application database or otherwise putting non-packagey things into it.</li> <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 to <a href="mailto:abuse@npmjs.com">abuse@npmjs.com</a> right +<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 +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 @@ -111,7 +111,7 @@ clear up any confusion with changes to their package's <code><a href="../../ 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> +the <a href="https://github.com/npm/cli/commits/latest/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> @@ -134,5 +134,5 @@ License.</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-disputes — npm@6.1.0</p> +<p id="footer">npm-disputes — npm@6.2.0</p> diff --git a/deps/npm/html/doc/misc/npm-index.html b/deps/npm/html/doc/misc/npm-index.html index d3c382a203..7c67f1b99a 100644 --- a/deps/npm/html/doc/misc/npm-index.html +++ b/deps/npm/html/doc/misc/npm-index.html @@ -180,5 +180,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@6.1.0</p> +<p id="footer">npm-index — npm@6.2.0</p> diff --git a/deps/npm/html/doc/misc/npm-orgs.html b/deps/npm/html/doc/misc/npm-orgs.html index 3ed6709f33..e2ed0d240c 100644 --- a/deps/npm/html/doc/misc/npm-orgs.html +++ b/deps/npm/html/doc/misc/npm-orgs.html @@ -29,46 +29,37 @@ <ul> <li>Check who you’ve added to your org:</li> </ul> -<pre><code>npm team ls <org>:developers -</code></pre><ul> +<pre><code>npm team ls <org>:developers</code></pre><ul> <li><p>Each org is automatically given a <code>developers</code> team, so you can see the whole list of team members in your org. This team automatically gets read-write access to all packages, but you can change that with the <code>access</code> command.</p> </li> <li><p>Create a new team:</p> </li> </ul> -<pre><code>npm team create <org:team> -</code></pre><ul> +<pre><code>npm team create <org:team></code></pre><ul> <li>Add members to that team:</li> </ul> -<pre><code>npm team add <org:team> <user> -</code></pre><h2 id="publish-a-package-and-adjust-package-access">Publish a package and adjust package access</h2> +<pre><code>npm team add <org:team> <user></code></pre><h2 id="publish-a-package-and-adjust-package-access">Publish a package and adjust package access</h2> <ul> <li>In package directory, run</li> </ul> -<pre><code>npm init --scope=<org> -</code></pre><p>to scope it for your org & publish as usual</p> +<pre><code>npm init --scope=<org></code></pre><p>to scope it for your org & publish as usual</p> <ul> <li>Grant access: </li> </ul> -<pre><code>npm access grant <read-only|read-write> <org:team> [<package>] -</code></pre><ul> +<pre><code>npm access grant <read-only|read-write> <org:team> [<package>]</code></pre><ul> <li>Revoke access:</li> </ul> -<pre><code>npm access revoke <org:team> [<package>] -</code></pre><h2 id="monitor-your-package-access">Monitor your package access</h2> +<pre><code>npm access revoke <org:team> [<package>]</code></pre><h2 id="monitor-your-package-access">Monitor your package access</h2> <ul> <li>See what org packages a team member can access:</li> </ul> -<pre><code>npm access ls-packages <org> <user> -</code></pre><ul> +<pre><code>npm access ls-packages <org> <user></code></pre><ul> <li>See packages available to a specific team:</li> </ul> -<pre><code>npm access ls-packages <org:team> -</code></pre><ul> +<pre><code>npm access ls-packages <org:team></code></pre><ul> <li>Check which teams are collaborating on a package:</li> </ul> -<pre><code>npm access ls-collaborators <pkg> -</code></pre><h2 id="see-also">SEE ALSO</h2> +<pre><code>npm access ls-collaborators <pkg></code></pre><h2 id="see-also">SEE ALSO</h2> <ul> <li><a href="../cli/npm-team.html">npm-team(1)</a></li> <li><a href="../cli/npm-access.html">npm-access(1)</a></li> @@ -86,5 +77,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@6.1.0</p> +<p id="footer">npm-orgs — npm@6.2.0</p> diff --git a/deps/npm/html/doc/misc/npm-registry.html b/deps/npm/html/doc/misc/npm-registry.html index f3f9704a87..1a5626646d 100644 --- a/deps/npm/html/doc/misc/npm-registry.html +++ b/deps/npm/html/doc/misc/npm-registry.html @@ -43,8 +43,8 @@ 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> +<p>The npm registry does not try 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 @@ -90,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@6.1.0</p> +<p id="footer">npm-registry — npm@6.2.0</p> diff --git a/deps/npm/html/doc/misc/npm-scope.html b/deps/npm/html/doc/misc/npm-scope.html index 7c285406b2..fe4a1abc25 100644 --- a/deps/npm/html/doc/misc/npm-scope.html +++ b/deps/npm/html/doc/misc/npm-scope.html @@ -15,8 +15,7 @@ follows the usual rules for package names (URL-safe characters, no leading dots or underscores). When used in package names, scopes are preceded by an <code>@</code> symbol and followed by a slash, e.g.</p> -<pre><code>@somescope/somepackagename -</code></pre><p>Scopes are a way of grouping related packages together, and also affect a few +<pre><code>@somescope/somepackagename</code></pre><p>Scopes are a way of grouping related packages together, and also affect a few things about the way npm treats the package.</p> <p>Each npm user/organization has their own scope, and only you can add packages in your scope. This means you don't have to worry about someone taking your @@ -34,18 +33,15 @@ folder (<code>@myorg</code>) is simply the name of the scope preceded by an <cod contain any number of scoped packages.</p> <p>A scoped package is installed by referencing it by name, preceded by an <code>@</code> symbol, in <code>npm install</code>:</p> -<pre><code>npm install @myorg/mypackage -</code></pre><p>Or in <code>package.json</code>:</p> +<pre><code>npm install @myorg/mypackage</code></pre><p>Or in <code>package.json</code>:</p> <pre><code>"dependencies": { "@myorg/mypackage": "^1.3.0" -} -</code></pre><p>Note that if the <code>@</code> symbol is omitted, in either case, npm will instead attempt to +}</code></pre><p>Note that if the <code>@</code> symbol is omitted, in either case, npm will instead attempt to install from GitHub; see <code><a href="../cli/npm-install.html">npm-install(1)</a></code>.</p> <h2 id="requiring-scoped-packages">Requiring scoped packages</h2> <p>Because scoped packages are installed into a scope folder, you have to include the name of the scope when requiring them in your code, e.g.</p> -<pre><code>require('@myorg/mypackage') -</code></pre><p>There is nothing special about the way Node treats scope folders. This +<pre><code>require('@myorg/mypackage')</code></pre><p>There is nothing special about the way Node treats scope folders. This simply requires the <code>mypackage</code> module in the folder named <code>@myorg</code>.</p> <h2 id="publishing-scoped-packages">Publishing scoped packages</h2> <p>Scoped packages can be published from the CLI as of <code>npm@2</code> and can be @@ -71,12 +67,10 @@ desired, with <code>npm access</code> or on the npmjs.com website.</p> seamlessly use a mix of packages from the primary npm registry and one or more private registries, such as npm Enterprise.</p> <p>You can associate a scope with a registry at login, e.g.</p> -<pre><code>npm login --registry=http://reg.example.com --scope=@myco -</code></pre><p>Scopes have a many-to-one relationship with registries: one registry can +<pre><code>npm login --registry=http://reg.example.com --scope=@myco</code></pre><p>Scopes have a many-to-one relationship with registries: one registry can host multiple scopes, but a scope only ever points to one registry.</p> <p>You can also associate a scope with a registry using <code>npm config</code>:</p> -<pre><code>npm config set @myco:registry http://reg.example.com -</code></pre><p>Once a scope is associated with a registry, any <code>npm install</code> for a package +<pre><code>npm config set @myco:registry http://reg.example.com</code></pre><p>Once a scope is associated with a registry, any <code>npm install</code> for a package with that scope will request packages from that registry instead. Any <code>npm publish</code> for a package name that contains the scope will be published to that registry instead.</p> @@ -99,5 +93,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@6.1.0</p> +<p id="footer">npm-scope — npm@6.2.0</p> diff --git a/deps/npm/html/doc/misc/npm-scripts.html b/deps/npm/html/doc/misc/npm-scripts.html index 43b0ca63e0..d76bba3b61 100644 --- a/deps/npm/html/doc/misc/npm-scripts.html +++ b/deps/npm/html/doc/misc/npm-scripts.html @@ -60,11 +60,11 @@ Run by the <code>npm shrinkwrap</code> command.</li> <p>Additionally, arbitrary scripts can be executed by running <code>npm run-script <stage></code>. <em>Pre</em> and <em>post</em> commands with matching 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> +<code>postmyscript</code>). Scripts from dependencies can be run with <code>npm explore +<pkg> -- npm run <stage></code>.</p> <h2 id="prepublish-and-prepare">PREPUBLISH AND PREPARE</h2> <h3 id="deprecation-note">DEPRECATION NOTE</h3> -<p>Since <a href="mailto:`npm@1.1.71">`npm@1.1.71</a><code>, the npm CLI has run the</code>prepublish<code>script for both</code>npm +<p>Since <a href="mailto:%60npm@1.1.71">`npm@1.1.71</a><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, [very @@ -125,8 +125,7 @@ suites, then those executables will be added to the <code>PATH</code> for executing the scripts. So, if your package.json has this:</p> <pre><code>{ "name" : "foo" , "dependencies" : { "bar" : "0.1.x" } -, "scripts": { "start" : "bar ./test" } } -</code></pre><p>then you could run <code>npm start</code> to execute the <code>bar</code> script, which is +, "scripts": { "start" : "bar ./test" } }</code></pre><p>then you could run <code>npm start</code> to execute the <code>bar</code> script, which is exported into the <code>node_modules/.bin</code> directory on <code>npm install</code>.</p> <h3 id="package-json-vars">package.json vars</h3> <p>The package.json fields are tacked onto the <code>npm_package_</code> prefix. So, @@ -144,12 +143,9 @@ there is a config param of <code><name>[@<version>]:<key></cod if the package.json has this:</p> <pre><code>{ "name" : "foo" , "config" : { "port" : "8080" } -, "scripts" : { "start" : "node server.js" } } -</code></pre><p>and the server.js is this:</p> -<pre><code>http.createServer(...).listen(process.env.npm_package_config_port) -</code></pre><p>then the user could change the behavior by doing:</p> -<pre><code>npm config set foo:port 80 -</code></pre><h3 id="current-lifecycle-event">current lifecycle event</h3> +, "scripts" : { "start" : "node server.js" } }</code></pre><p>and the server.js is this:</p> +<pre><code>http.createServer(...).listen(process.env.npm_package_config_port)</code></pre><p>then the user could change the behavior by doing:</p> +<pre><code>npm config set foo:port 80</code></pre><h3 id="current-lifecycle-event">current lifecycle event</h3> <p>Lastly, the <code>npm_lifecycle_event</code> environment variable is set to whichever stage of the cycle is being executed. So, you could have a single script used for different parts of the process which switches @@ -157,16 +153,14 @@ based on what's currently happening.</p> <p>Objects are flattened following this format, so if you had <code>{"scripts":{"install":"foo.js"}}</code> in your package.json, then you'd see this in the script:</p> -<pre><code>process.env.npm_package_scripts_install === "foo.js" -</code></pre><h2 id="examples">EXAMPLES</h2> +<pre><code>process.env.npm_package_scripts_install === "foo.js"</code></pre><h2 id="examples">EXAMPLES</h2> <p>For example, if your package.json contains this:</p> <pre><code>{ "scripts" : { "install" : "scripts/install.js" , "postinstall" : "scripts/install.js" , "uninstall" : "scripts/uninstall.js" } -} -</code></pre><p>then <code>scripts/install.js</code> will be called for the install +}</code></pre><p>then <code>scripts/install.js</code> will be called for the install and post-install stages of the lifecycle, and <code>scripts/uninstall.js</code> will be called when the package is uninstalled. Since <code>scripts/install.js</code> is running for two different phases, it would @@ -179,8 +173,7 @@ fine:</p> , "install" : "make && make install" , "test" : "make test" } -} -</code></pre><h2 id="exiting">EXITING</h2> +}</code></pre><h2 id="exiting">EXITING</h2> <p>Scripts are run by passing the line as a script argument to <code>sh</code>.</p> <p>If the script exits with a code other than 0, then this will abort the process.</p> @@ -239,5 +232,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@6.1.0</p> +<p id="footer">npm-scripts — npm@6.2.0</p> diff --git a/deps/npm/html/doc/misc/removing-npm.html b/deps/npm/html/doc/misc/removing-npm.html index 15077119ab..3abcf7adb1 100644 --- a/deps/npm/html/doc/misc/removing-npm.html +++ b/deps/npm/html/doc/misc/removing-npm.html @@ -12,10 +12,8 @@ <h1><a href="../cli/npm-removal.html">npm-removal</a></h1> <p>Cleaning the Slate</p> <h2 id="synopsis">SYNOPSIS</h2> <p>So sad to see you go.</p> -<pre><code>sudo npm uninstall npm -g -</code></pre><p>Or, if that fails, get the npm source code, and do:</p> -<pre><code>sudo make uninstall -</code></pre><h2 id="more-severe-uninstalling">More Severe Uninstalling</h2> +<pre><code>sudo npm uninstall npm -g</code></pre><p>Or, if that fails, get the npm source code, and do:</p> +<pre><code>sudo make uninstall</code></pre><h2 id="more-severe-uninstalling">More Severe Uninstalling</h2> <p>Usually, the above instructions are sufficient. That will remove npm, but leave behind anything you've installed.</p> <p>If that doesn't work, or if you require more drastic measures, @@ -29,16 +27,13 @@ you configured node with a different <code>--prefix</code>, or installed npm wit different prefix setting, then adjust the paths accordingly, replacing <code>/usr/local</code> with your install prefix.</p> <p>To remove everything npm-related manually:</p> -<pre><code>rm -rf /usr/local/{lib/node{,/.npm,_modules},bin,share/man}/npm* -</code></pre><p>If you installed things <em>with</em> npm, then your best bet is to uninstall +<pre><code>rm -rf /usr/local/{lib/node{,/.npm,_modules},bin,share/man}/npm*</code></pre><p>If you installed things <em>with</em> npm, then your best bet is to uninstall them with npm first, and then install them again once you have a proper install. This can help find any symlinks that are lying around:</p> -<pre><code>ls -laF /usr/local/{lib/node{,/.npm},bin,share/man} | grep npm -</code></pre><p>Prior to version 0.3, npm used shim files for executables and node +<pre><code>ls -laF /usr/local/{lib/node{,/.npm},bin,share/man} | grep npm</code></pre><p>Prior to version 0.3, npm used shim files for executables and node modules. To track those down, you can do the following:</p> -<pre><code>find /usr/local/{lib/node,bin} -exec grep -l npm \{\} \; ; -</code></pre><p>(This is also in the <a href="../../doc/README.html">README</a> file.)</p> +<pre><code>find /usr/local/{lib/node,bin} -exec grep -l npm \{\} \; ;</code></pre><p>(This is also in the <a href="../../doc/README.html">README</a> file.)</p> <h2 id="see-also">SEE ALSO</h2> <ul> <li><a href="../../doc/README.html">README</a></li> @@ -57,5 +52,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@6.1.0</p> +<p id="footer">removing-npm — npm@6.2.0</p> diff --git a/deps/npm/html/doc/misc/semver.html b/deps/npm/html/doc/misc/semver.html index b3a69fbce3..028d50aade 100644 --- a/deps/npm/html/doc/misc/semver.html +++ b/deps/npm/html/doc/misc/semver.html @@ -11,12 +11,11 @@ <h1><a href="../misc/semver.html">semver</a></h1> <p>The semantic versioner for npm</p> <h2 id="install">Install</h2> -<pre><code class="lang-bash">npm install --save semver -` -</code></pre> +<pre><code class="language-bash">npm install --save semver +`</code></pre> <h2 id="usage">Usage</h2> <p>As a node module:</p> -<pre><code class="lang-js">const semver = require('semver') +<pre><code class="language-js">const semver = require('semver') semver.valid('1.2.3') // '1.2.3' semver.valid('a.b.c') // null @@ -25,8 +24,7 @@ semver.satisfies('1.2.3', '1.x || >=2.5.0 || 5.0.0 - 7.2.3') semver.gt('1.2.3', '9.8.7') // false semver.lt('1.2.3', '9.8.7') // true semver.valid(semver.coerce('v2')) // '2.0.0' -semver.valid(semver.coerce('42.6.7.9.3-alpha')) // '42.6.7' -</code></pre> +semver.valid(semver.coerce('42.6.7.9.3-alpha')) // '42.6.7'</code></pre> <p>As a command-line utility:</p> <pre><code>$ semver -h @@ -65,8 +63,7 @@ all supplied ranges, and prints all satisfying versions. If no satisfying versions are found, then exits failure. Versions are printed in ascending order, so supplying -multiple versions to the utility will just sort them. -</code></pre><h2 id="versions">Versions</h2> +multiple versions to the utility will just sort them.</code></pre><h2 id="versions">Versions</h2> <p>A "version" is described by the <code>v2.0.0</code> specification found at <a href="http://semver.org/">http://semver.org/</a>.</p> <p>A leading <code>"="</code> or <code>"v"</code> character is stripped off and ignored.</p> @@ -123,17 +120,14 @@ similar risk on the <em>next</em> set of prerelease versions.</p> <h4 id="prerelease-identifiers">Prerelease Identifiers</h4> <p>The method <code>.inc</code> takes an additional <code>identifier</code> string argument that will append the value of the string as a prerelease identifier:</p> -<pre><code class="lang-javascript">semver.inc('1.2.3', 'prerelease', 'beta') -// '1.2.4-beta.0' -</code></pre> +<pre><code class="language-javascript">semver.inc('1.2.3', 'prerelease', 'beta') +// '1.2.4-beta.0'</code></pre> <p>command-line example:</p> -<pre><code class="lang-bash">$ semver 1.2.3 -i prerelease --preid beta -1.2.4-beta.0 -</code></pre> +<pre><code class="language-bash">$ semver 1.2.3 -i prerelease --preid beta +1.2.4-beta.0</code></pre> <p>Which then can be used to increment further:</p> -<pre><code class="lang-bash">$ semver 1.2.4-beta.0 -i prerelease -1.2.4-beta.1 -</code></pre> +<pre><code class="language-bash">$ semver 1.2.4-beta.0 -i prerelease +1.2.4-beta.1</code></pre> <h3 id="advanced-range-syntax">Advanced Range Syntax</h3> <p>Advanced range syntax desugars to primitive comparators in deterministic ways.</p> @@ -231,7 +225,7 @@ zero.</p> <h3 id="range-grammar">Range Grammar</h3> <p>Putting all this together, here is a Backus-Naur grammar for ranges, for the benefit of parser authors:</p> -<pre><code class="lang-bnf">range-set ::= range ( logical-or range ) * +<pre><code class="language-bnf">range-set ::= range ( logical-or range ) * logical-or ::= ( ' ' ) * '||' ( ' ' ) * range ::= hyphen | simple ( ' ' simple ) * | '' hyphen ::= partial ' - ' partial @@ -246,8 +240,7 @@ qualifier ::= ( '-' pre )? ( '+' build )? pre ::= parts build ::= parts parts ::= part ( '.' part ) * -part ::= nr | [-0-9A-Za-z]+ -</code></pre> +part ::= nr | [-0-9A-Za-z]+</code></pre> <h2 id="functions">Functions</h2> <p>All methods and classes take a final <code>loose</code> boolean argument that, if true, will be more forgiving about not-quite-valid semver strings. @@ -357,5 +350,5 @@ higher value components are invalid (<code>9999999999999999.4.7.4</code> is like <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@6.1.0</p> +<p id="footer">semver — npm@6.2.0</p> |