Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/nodejs/node.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
path: root/deps/npm/docs/output/commands
diff options
context:
space:
mode:
authorRuy Adorno <ruyadorno@hotmail.com>2021-01-29 01:38:39 +0300
committerRuy Adorno <ruyadorno@hotmail.com>2021-01-30 07:49:44 +0300
commitd3906ae29414430c5df28858e23783b91b15ab52 (patch)
tree93dbcc6025283827c2e88e92401a5102808c265b /deps/npm/docs/output/commands
parent0a993e1f24beea678769bc07099f05a1ed27334d (diff)
deps: upgrade npm to 7.5.0
PR-URL: https://github.com/nodejs/node/pull/37117 Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Yongsheng Zhang <zyszys98@gmail.com> Reviewed-By: Juan José Arboleda <soyjuanarbol@gmail.com>
Diffstat (limited to 'deps/npm/docs/output/commands')
-rw-r--r--deps/npm/docs/output/commands/npm-diff.html346
-rw-r--r--deps/npm/docs/output/commands/npm-exec.html16
-rw-r--r--deps/npm/docs/output/commands/npm-init.html17
-rw-r--r--deps/npm/docs/output/commands/npm-ls.html2
-rw-r--r--deps/npm/docs/output/commands/npm-owner.html1
-rw-r--r--deps/npm/docs/output/commands/npm-run-script.html38
-rw-r--r--deps/npm/docs/output/commands/npm-search.html6
-rw-r--r--deps/npm/docs/output/commands/npm-update.html26
-rw-r--r--deps/npm/docs/output/commands/npm-version.html21
-rw-r--r--deps/npm/docs/output/commands/npm-view.html36
-rw-r--r--deps/npm/docs/output/commands/npm.html104
11 files changed, 508 insertions, 105 deletions
diff --git a/deps/npm/docs/output/commands/npm-diff.html b/deps/npm/docs/output/commands/npm-diff.html
new file mode 100644
index 00000000000..43840ea9a29
--- /dev/null
+++ b/deps/npm/docs/output/commands/npm-diff.html
@@ -0,0 +1,346 @@
+<html><head>
+<title>npm-diff</title>
+<style>
+body {
+ background-color: #ffffff;
+ color: #24292e;
+
+ margin: 0;
+
+ line-height: 1.5;
+
+ font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji";
+}
+#rainbar {
+ height: 10px;
+ background-image: linear-gradient(139deg, #fb8817, #ff4b01, #c12127, #e02aff);
+}
+
+a {
+ text-decoration: none;
+ color: #0366d6;
+}
+a:hover {
+ text-decoration: underline;
+}
+
+pre {
+ margin: 1em 0px;
+ padding: 1em;
+ border: solid 1px #e1e4e8;
+ border-radius: 6px;
+
+ display: block;
+ overflow: auto;
+
+ white-space: pre;
+
+ background-color: #f6f8fa;
+ color: #393a34;
+}
+code {
+ font-family: SFMono-Regular, Consolas, "Liberation Mono", Menlo, Courier, monospace;
+ font-size: 85%;
+ padding: 0.2em 0.4em;
+ background-color: #f6f8fa;
+ color: #393a34;
+}
+pre > code {
+ padding: 0;
+ background-color: inherit;
+ color: inherit;
+}
+h1, h2, h3 {
+ font-weight: 600;
+}
+
+#logobar {
+ background-color: #333333;
+ margin: 0 auto;
+ padding: 1em 4em;
+}
+#logobar .logo {
+ float: left;
+}
+#logobar .title {
+ font-weight: 600;
+ color: #dddddd;
+ float: left;
+ margin: 5px 0 0 1em;
+}
+#logobar:after {
+ content: "";
+ display: block;
+ clear: both;
+}
+
+#content {
+ margin: 0 auto;
+ padding: 0 4em;
+}
+
+#table_of_contents > h2 {
+ font-size: 1.17em;
+}
+#table_of_contents ul:first-child {
+ border: solid 1px #e1e4e8;
+ border-radius: 6px;
+ padding: 1em;
+ background-color: #f6f8fa;
+ color: #393a34;
+}
+#table_of_contents ul {
+ list-style-type: none;
+ padding-left: 1.5em;
+}
+#table_of_contents li {
+ font-size: 0.9em;
+}
+#table_of_contents li a {
+ color: #000000;
+}
+
+header.title {
+ border-bottom: solid 1px #e1e4e8;
+}
+header.title > h1 {
+ margin-bottom: 0.25em;
+}
+header.title > .description {
+ display: block;
+ margin-bottom: 0.5em;
+ line-height: 1;
+}
+
+footer#edit {
+ border-top: solid 1px #e1e4e8;
+ margin: 3em 0 4em 0;
+ padding-top: 2em;
+}
+</style>
+</head>
+<body>
+<div id="banner">
+<div id="rainbar"></div>
+<div id="logobar">
+<svg class="logo" role="img" height="32" width="32" viewBox="0 0 700 700">
+<polygon fill="#cb0000" points="0,700 700,700 700,0 0,0"></polygon>
+<polygon fill="#ffffff" points="150,550 350,550 350,250 450,250 450,550 550,550 550,150 150,150"></polygon>
+</svg>
+<div class="title">
+npm command-line interface
+</div>
+</div>
+</div>
+
+<section id="content">
+<header class="title">
+<h1 id="npm-diff">npm-diff</h1>
+<span class="description">The registry diff command</span>
+</header>
+
+<section id="table_of_contents">
+<h2 id="table-of-contents">Table of contents</h2>
+<div id="_table_of_contents"><ul><li><a href="#see-also">See Also</a></li></ul></div>
+</section>
+
+<div id="_content"><h3 id="synopsis">Synopsis</h3>
+<pre lang="bash"><code>npm diff [...&lt;paths&gt;]
+npm diff --diff=&lt;pkg-name&gt; [...&lt;paths&gt;]
+npm diff --diff=&lt;version-a&gt; [--diff=&lt;version-b&gt;] [...&lt;paths&gt;]
+npm diff --diff=&lt;spec-a&gt; [--diff=&lt;spec-b&gt;] [...&lt;paths&gt;]
+npm diff [--diff-ignore-all-space] [--diff-name-only] [...&lt;paths&gt;]
+</code></pre>
+<h3 id="description">Description</h3>
+<p>Similar to its <code>git diff</code> counterpart, this command will print diff patches
+of files for packages published to the npm registry.</p>
+<ul>
+<li>
+<p><code>npm diff --diff=&lt;spec-a&gt; --diff=&lt;spec-b&gt;</code></p>
+<p>Compares two package versions using their registry specifiers, e.g:
+<code>npm diff --diff=pkg@1.0.0 --diff=pkg@^2.0.0</code>. It’s also possible to
+compare across forks of any package,
+e.g: <code>npm diff --diff=pkg@1.0.0 --diff=pkg-fork@1.0.0</code>.</p>
+<p>Any valid spec can be used, so that it’s also possible to compare
+directories or git repositories,
+e.g: <code>npm diff --diff=pkg@latest --diff=./packages/pkg</code></p>
+<p>Here’s an example comparing two different versions of a package named
+<code>abbrev</code> from the registry:</p>
+<pre lang="bash"><code>npm diff --diff=abbrev@1.1.0 --diff=abbrev@1.1.1
+</code></pre>
+<p>On success, output looks like:</p>
+<pre lang="bash"><code>diff --git a/package.json b/package.json
+index v1.1.0..v1.1.1 100644
+--- a/package.json
++++ b/package.json
+@@ -1,6 +1,6 @@
+ {
+ "name": "abbrev",
+- "version": "1.1.0",
++ "version": "1.1.1",
+ "description": "Like ruby's abbrev module, but in js",
+ "author": "Isaac Z. Schlueter &lt;i@izs.me&gt;",
+ "main": "abbrev.js",
+</code></pre>
+<p>Given the flexible nature of npm specs, you can also target local
+directories or git repos just like when using <code>npm install</code>:</p>
+<pre lang="bash"><code>npm diff --diff=https://github.com/npm/libnpmdiff --diff=./local-path
+</code></pre>
+<p>In the example above we can compare the contents from the package installed
+from the git repo at <code>github.com/npm/libnpmdiff</code> with the contents of the
+<code>./local-path</code> that contains a valid package, such as a modified copy of
+the original.</p>
+</li>
+<li>
+<p><code>npm diff</code> (in a package directory, no arguments):</p>
+<p>If the package is published to the registry, <code>npm diff</code> will fetch the
+tarball version tagged as <code>latest</code> (this value can be configured using the
+<code>tag</code> option) and proceed to compare the contents of files present in that
+tarball, with the current files in your local file system.</p>
+<p>This workflow provides a handy way for package authors to see what
+package-tracked files have been changed in comparison with the latest
+published version of that package.</p>
+</li>
+<li>
+<p><code>npm diff --diff=&lt;pkg-name&gt;</code> (in a package directory):</p>
+<p>When using a single package name (with no version or tag specifier) as an
+argument, <code>npm diff</code> will work in a similar way to
+<a href="npm-outdated"><code>npm-outdated</code></a> and reach for the registry to figure out
+what current published version of the package named <!-- raw HTML omitted --> will satisfy
+its dependent declared semver-range. Once that specific version is known
+<code>npm diff</code> will print diff patches comparing the current version of
+<!-- raw HTML omitted --> found in the local file system with that specific version
+returned by the registry.</p>
+<p>Given a package named <code>abbrev</code> that is currently installed:</p>
+<pre lang="bash"><code>npm diff --diff=abbrev
+</code></pre>
+<p>That will request from the registry its most up to date version and
+will print a diff output comparing the currently installed version to this
+newer one if the version numbers are not the same.</p>
+</li>
+<li>
+<p><code>npm diff --diff=&lt;spec-a&gt;</code> (in a package directory):</p>
+<p>Similar to using only a single package name, it’s also possible to declare
+a full registry specifier version if you wish to compare the local version
+of an installed package with the specific version/tag/semver-range provided
+in <code>&lt;spec-a&gt;</code>.</p>
+<p>An example: assuming <code>pkg@1.0.0</code> is installed in the current <code>node_modules</code>
+folder, running:</p>
+<pre lang="bash"><code>npm diff --diff=pkg@2.0.0
+</code></pre>
+<p>It will effectively be an alias to
+<code>npm diff --diff=pkg@1.0.0 --diff=pkg@2.0.0</code>.</p>
+</li>
+<li>
+<p><code>npm diff --diff=&lt;semver-a&gt; [--diff=&lt;semver-b&gt;]</code> (in a package directory):</p>
+<p>Using <code>npm diff</code> along with semver-valid version numbers is a shorthand
+to compare different versions of the current package.</p>
+<p>It needs to be run from a package directory, such that for a package named
+<code>pkg</code> running <code>npm diff --diff=1.0.0 --diff=1.0.1</code> is the same as running
+<code>npm diff --diff=pkg@1.0.0 --diff=pkg@1.0.1</code>.</p>
+<p>If only a single argument <code>&lt;version-a&gt;</code> is provided, then the current local
+file system is going to be compared against that version.</p>
+<p>Here’s an example comparing two specific versions (published to the
+configured registry) of the current project directory:</p>
+<pre lang="bash"><code>npm diff --diff=1.0.0 --diff=1.1.0
+</code></pre>
+</li>
+</ul>
+<p>Note that tag names are not valid <code>--diff</code> argument values, if you wish to
+compare to a published tag, you must use the <code>pkg@tagname</code> syntax.</p>
+<h4 id="filtering-files">Filtering files</h4>
+<p>It’s possible to also specify positional arguments using file names or globs
+pattern matching in order to limit the result of diff patches to only a subset
+of files for a given package, e.g:</p>
+<pre lang="bash"><code>npm diff --diff=pkg@2 ./lib/ CHANGELOG.md
+</code></pre>
+<p>In the example above the diff output is only going to print contents of files
+located within the folder <code>./lib/</code> and changed lines of code within the
+<code>CHANGELOG.md</code> file.</p>
+<h3 id="configuration">Configuration</h3>
+<h4 id="diff">diff</h4>
+<ul>
+<li>Type: Array<!-- raw HTML omitted --></li>
+<li>Default: null</li>
+</ul>
+<p>Defines npm package specifiers to compare using the <code>npm diff</code> command.</p>
+<p>This can be specified up to 2 times.</p>
+<h4 id="diff-name-only">diff-name-only</h4>
+<ul>
+<li>Type: Boolean</li>
+<li>Default: false</li>
+</ul>
+<p>When set to <code>true</code> running <code>npm diff</code> only returns the names of the files that
+have any difference.</p>
+<h4 id="diff-unified">diff-unified</h4>
+<ul>
+<li>Type: Number</li>
+<li>Default: <code>3</code></li>
+</ul>
+<p>The number of lines of context to print in the unified diff format output.</p>
+<h4 id="diff-ignore-all-space">diff-ignore-all-space</h4>
+<ul>
+<li>Type: Boolean</li>
+<li>Default: false</li>
+</ul>
+<p>Ignore whitespace when comparing lines. This ignores differences even if one
+line has whitespace where the other line has none.</p>
+<h4 id="diff-no-prefix">diff-no-prefix</h4>
+<ul>
+<li>Type: Boolean</li>
+<li>Default: false</li>
+</ul>
+<p>Do not show any source or destination prefix.</p>
+<h4 id="diff-src-prefix">diff-src-prefix</h4>
+<ul>
+<li>Type: String</li>
+<li>Default: <code>"a/"</code></li>
+</ul>
+<p>Show the given source prefix in diff patches headers instead of using “a/”.</p>
+<h4 id="diff-dst-prefix">diff-dst-prefix</h4>
+<ul>
+<li>Type: String</li>
+<li>Default: <code>"b/"</code></li>
+</ul>
+<p>Show the given source prefix in diff patches headers instead of using “b/”.</p>
+<h4 id="diff-text">diff-text</h4>
+<ul>
+<li>Type: Boolean</li>
+<li>Default: false</li>
+</ul>
+<p>Treat all files as text.</p>
+<h4 id="global">global</h4>
+<ul>
+<li>Default: false</li>
+<li>Type: Boolean</li>
+</ul>
+<p>Uses packages from the global space as a source for comparison.</p>
+<h4 id="tag">tag</h4>
+<ul>
+<li>Type: String</li>
+<li>Default: <code>"latest"</code></li>
+</ul>
+<p>The tag used to fetch the tarball that will be compared with the local file
+system files when running npm diff with no arguments.</p>
+<h2 id="see-also">See Also</h2>
+<ul>
+<li><a href="../commands/npm-outdated.html">npm outdated</a></li>
+<li><a href="../commands/npm-install.html">npm install</a></li>
+<li><a href="../commands/npm-config.html">npm config</a></li>
+<li><a href="../using-npm/registry.html">npm registry</a></li>
+</ul>
+</div>
+
+<footer id="edit">
+<a href="https://github.com/npm/cli/edit/latest/docs/content/commands/npm-diff.md">
+<svg role="img" viewBox="0 0 16 16" width="16" height="16" fill="currentcolor" style="vertical-align: text-bottom; margin-right: 0.3em;">
+<path fill-rule="evenodd" d="M11.013 1.427a1.75 1.75 0 012.474 0l1.086 1.086a1.75 1.75 0 010 2.474l-8.61 8.61c-.21.21-.47.364-.756.445l-3.251.93a.75.75 0 01-.927-.928l.929-3.25a1.75 1.75 0 01.445-.758l8.61-8.61zm1.414 1.06a.25.25 0 00-.354 0L10.811 3.75l1.439 1.44 1.263-1.263a.25.25 0 000-.354l-1.086-1.086zM11.189 6.25L9.75 4.81l-6.286 6.287a.25.25 0 00-.064.108l-.558 1.953 1.953-.558a.249.249 0 00.108-.064l6.286-6.286z"></path>
+</svg>
+Edit this page on GitHub
+</a>
+</footer>
+</section>
+
+
+
+</body></html> \ No newline at end of file
diff --git a/deps/npm/docs/output/commands/npm-exec.html b/deps/npm/docs/output/commands/npm-exec.html
index ecee5f01434..03059c52052 100644
--- a/deps/npm/docs/output/commands/npm-exec.html
+++ b/deps/npm/docs/output/commands/npm-exec.html
@@ -141,7 +141,7 @@ npm command-line interface
<section id="table_of_contents">
<h2 id="table-of-contents">Table of contents</h2>
-<div id="_table_of_contents"><ul><li><a href="#synopsis">Synopsis</a></li><li><a href="#description">Description</a></li><li><a href="#npx-vs-npm-exec"><code>npx</code> vs <code>npm exec</code></a></li><li><a href="#examples">Examples</a></li><li><a href="#compatibility-with-older-npx-versions">Compatibility with Older npx Versions</a></li><li><a href="#see-also">See Also</a></li></ul></div>
+<div id="_table_of_contents"><ul><li><a href="#synopsis">Synopsis</a></li><li><a href="#description">Description</a></li><li><a href="#npx-vs-npm-exec"><code>npx</code> vs <code>npm exec</code></a></li><li><a href="#examples">Examples</a></li><li><a href="#compatibility-with-older-npx-versions">Compatibility with Older npx Versions</a></li><li><a href="#a-note-on-caching">A note on caching</a></li><ul><li><a href="#prefer-online">prefer-online</a></li><li><a href="#prefer-offline">prefer-offline</a></li><li><a href="#offline">offline</a></li></ul><li><a href="#see-also">See Also</a></li></ul></div>
</section>
<div id="_content"><h3 id="synopsis">Synopsis</h3>
@@ -273,6 +273,20 @@ with.</li>
<li>The <code>--shell</code> option is replaced with <code>--script-shell</code>, but maintained
in the <code>npx</code> executable for backwards compatibility.</li>
</ul>
+<h3 id="a-note-on-caching">A note on caching</h3>
+<p>The npm cli utilizes its internal package cache when using the package
+name specified. You can use the following to change how and when the
+cli uses this cache. See <a href="../commands/npm-cache.html"><code>npm cache</code></a> for more on
+how the cache works.</p>
+<h4 id="prefer-online">prefer-online</h4>
+<p>Forces staleness checks for packages, making the cli look for updates
+immediately even if the package is already in the cache.</p>
+<h4 id="prefer-offline">prefer-offline</h4>
+<p>Bypasses staleness checks for packages. Missing data will still be
+requested from the server. To force full offline mode, use <code>offline</code>.</p>
+<h4 id="offline">offline</h4>
+<p>Forces full offline mode. Any packages not locally cached will result in
+an error.</p>
<h3 id="see-also">See Also</h3>
<ul>
<li><a href="../commands/npm-run-script.html">npm run-script</a></li>
diff --git a/deps/npm/docs/output/commands/npm-init.html b/deps/npm/docs/output/commands/npm-init.html
index 0284b365398..3abf8e967b4 100644
--- a/deps/npm/docs/output/commands/npm-init.html
+++ b/deps/npm/docs/output/commands/npm-init.html
@@ -141,7 +141,7 @@ npm command-line interface
<section id="table_of_contents">
<h2 id="table-of-contents">Table of contents</h2>
-<div id="_table_of_contents"><ul><li><a href="#synopsis">Synopsis</a></li><li><a href="#description">Description</a></li><li><a href="#examples">Examples</a></li><li><a href="#see-also">See Also</a></li></ul></div>
+<div id="_table_of_contents"><ul><li><a href="#synopsis">Synopsis</a></li><li><a href="#description">Description</a></li><li><a href="#examples">Examples</a></li><li><a href="#a-note-on-caching">A note on caching</a></li><ul><li><a href="#prefer-online">prefer-online</a></li><li><a href="#prefer-offline">prefer-offline</a></li><li><a href="#offline">offline</a></li></ul><li><a href="#see-also">See Also</a></li></ul></div>
</section>
<div id="_content"><h3 id="synopsis">Synopsis</h3>
@@ -189,12 +189,27 @@ $ npm init
<p>Generate it without having it ask any questions:</p>
<pre lang="bash"><code>$ npm init -y
</code></pre>
+<h3 id="a-note-on-caching">A note on caching</h3>
+<p>The npm cli utilizes its internal package cache when using the package
+name specified. You can use the following to change how and when the
+cli uses this cache. See <a href="../commands/npm-cache.html"><code>npm cache</code></a> for more on
+how the cache works.</p>
+<h4 id="prefer-online">prefer-online</h4>
+<p>Forces staleness checks for packages, making the cli look for updates
+immediately even if the package is already in the cache.</p>
+<h4 id="prefer-offline">prefer-offline</h4>
+<p>Bypasses staleness checks for packages. Missing data will still be
+requested from the server. To force full offline mode, use <code>offline</code>.</p>
+<h4 id="offline">offline</h4>
+<p>Forces full offline mode. Any packages not locally cached will result in
+an error.</p>
<h3 id="see-also">See Also</h3>
<ul>
<li><a href="http://npm.im/init-package-json">init-package-json module</a></li>
<li><a href="../configuring-npm/package-json.html">package.json</a></li>
<li><a href="../commands/npm-version.html">npm version</a></li>
<li><a href="../using-npm/scope.html">npm scope</a></li>
+<li><a href="../commands/npm-exec.html">npm exec</a></li>
</ul>
</div>
diff --git a/deps/npm/docs/output/commands/npm-ls.html b/deps/npm/docs/output/commands/npm-ls.html
index 15d1bbc99f4..7cfa5a8ce4d 100644
--- a/deps/npm/docs/output/commands/npm-ls.html
+++ b/deps/npm/docs/output/commands/npm-ls.html
@@ -159,7 +159,7 @@ tree at all, use <a href="../commands/npm-explain.html"><code>npm explain</code>
the results to only the paths to the packages named. Note that nested
packages will <em>also</em> show the paths to the specified packages. For
example, running <code>npm ls promzard</code> in npm’s source tree will show:</p>
-<pre lang="bash"><code>npm@7.4.3 /path/to/npm
+<pre lang="bash"><code>npm@7.5.0 /path/to/npm
└─┬ init-package-json@0.0.4
└── promzard@0.1.5
</code></pre>
diff --git a/deps/npm/docs/output/commands/npm-owner.html b/deps/npm/docs/output/commands/npm-owner.html
index 625d3be234b..77f072da40b 100644
--- a/deps/npm/docs/output/commands/npm-owner.html
+++ b/deps/npm/docs/output/commands/npm-owner.html
@@ -173,7 +173,6 @@ on the command line when changing ownership with <code>--otp</code>.</p>
<li><a href="../commands/npm-publish.html">npm publish</a></li>
<li><a href="../using-npm/registry.html">npm registry</a></li>
<li><a href="../commands/npm-adduser.html">npm adduser</a></li>
-<li><a href="../using-npm/disputes.html">npm disputes</a></li>
</ul>
</div>
diff --git a/deps/npm/docs/output/commands/npm-run-script.html b/deps/npm/docs/output/commands/npm-run-script.html
index 57f6e6e2b65..a78a434760b 100644
--- a/deps/npm/docs/output/commands/npm-run-script.html
+++ b/deps/npm/docs/output/commands/npm-run-script.html
@@ -141,7 +141,7 @@ npm command-line interface
<section id="table_of_contents">
<h2 id="table-of-contents">Table of contents</h2>
-<div id="_table_of_contents"><ul><li><a href="#synopsis">Synopsis</a></li><li><a href="#description">Description</a></li><li><a href="#see-also">See Also</a></li></ul></div>
+<div id="_table_of_contents"><ul><li><a href="#synopsis">Synopsis</a></li><li><a href="#description">Description</a></li><li><a href="#configuration">Configuration</a></li><ul><li><a href="#if-present">if-present</a></li><li><a href="#ignore-scripts">ignore-scripts</a></li><li><a href="#script-shell">script-shell</a></li><li><a href="#silent">silent</a></li></ul><li><a href="#see-also">See Also</a></li></ul></div>
</section>
<div id="_content"><h3 id="synopsis">Synopsis</h3>
@@ -162,7 +162,7 @@ pass <code>-</code>-prefixed flags and options which would otherwise be parsed b
<pre lang="bash"><code>npm run test -- --grep="pattern"
</code></pre>
<p>The arguments will only be passed to the script specified after <code>npm run</code>
-and not to any pre or post script.</p>
+and not to any <code>pre</code> or <code>post</code> script.</p>
<p>The <code>env</code> script is a special built-in command that can be used to list
environment variables that will be available to the script at runtime. If an
“env” command is defined in your package, it will take precedence over the
@@ -178,7 +178,8 @@ provided by locally-installed dependencies can be used without the
<pre lang="bash"><code>"scripts": {"test": "node_modules/.bin/tap test/*.js"}
</code></pre>
<p>The actual shell your script is run within is platform dependent. By default,
-on Unix-like systems it is the <code>/bin/sh</code> command, on Windows it is the <code>cmd.exe</code>.
+on Unix-like systems it is the <code>/bin/sh</code> command, on Windows it is
+<code>cmd.exe</code>.
The actual shell referred to by <code>/bin/sh</code> also depends on the system.
You can customize the shell with the <code>script-shell</code> configuration.</p>
<p>Scripts are run from the root of the package folder, regardless of what the
@@ -192,12 +193,37 @@ passed, the directory within which <code>node</code> resides is added to the <co
If <code>--scripts-prepend-node-path=auto</code> is passed (which has been the default
in <code>npm</code> v3), this is only performed when that <code>node</code> executable is not
found in the <code>PATH</code>.</p>
-<p>If you try to run a script without having a <code>node_modules</code> directory and it fails,
-you will be given a warning to run <code>npm install</code>, just in case you’ve forgotten.</p>
-<p>You can use the <code>--silent</code> flag to prevent showing <code>npm ERR!</code> output on error.</p>
+<p>If you try to run a script without having a <code>node_modules</code> directory and it
+fails, you will be given a warning to run <code>npm install</code>, just in case you’ve
+forgotten.</p>
+<h3 id="configuration">Configuration</h3>
+<h4 id="if-present">if-present</h4>
+<ul>
+<li>Type: Boolean</li>
+<li>Default: false</li>
+</ul>
<p>You can use the <code>--if-present</code> flag to avoid exiting with a non-zero exit code
when the script is undefined. This lets you run potentially undefined scripts
without breaking the execution chain.</p>
+<h4 id="ignore-scripts">ignore-scripts</h4>
+<ul>
+<li>Type: Boolean</li>
+<li>Default: false</li>
+</ul>
+<p>Skips running <code>pre</code> and <code>post</code> scripts.</p>
+<h4 id="script-shell">script-shell</h4>
+<ul>
+<li>Type: String</li>
+<li>Default: <code>null</code></li>
+</ul>
+<p>Optional custom script to use to execute the command. If not defined defaults
+to <code>/bin/sh</code> on Unix, defaults to <code>env.comspec</code> or <code>cmd.exe</code> on Windows.</p>
+<h4 id="silent">silent</h4>
+<ul>
+<li>Type: Boolean</li>
+<li>Default: false</li>
+</ul>
+<p>You can use the <code>--silent</code> flag to prevent showing <code>npm ERR!</code> output on error.</p>
<h3 id="see-also">See Also</h3>
<ul>
<li><a href="../using-npm/scripts.html">npm scripts</a></li>
diff --git a/deps/npm/docs/output/commands/npm-search.html b/deps/npm/docs/output/commands/npm-search.html
index bad81ffa002..bd152230503 100644
--- a/deps/npm/docs/output/commands/npm-search.html
+++ b/deps/npm/docs/output/commands/npm-search.html
@@ -230,11 +230,11 @@ locally in its cache. You can use the following to change how and when
the cli uses this cache. See <a href="../commands/npm-cache.html"><code>npm cache</code></a> for more
on how the cache works.</p>
<h4 id="prefer-online">prefer-online</h4>
-<p>Forced staleness checks for cached searches, making the cli look for
+<p>Forces staleness checks for cached searches, making the cli look for
updates immediately even for fresh search results.</p>
<h4 id="prefer-offline">prefer-offline</h4>
-<p>Bypasses staleness checks for cached. Missing data will still be
-requested from the server. To force full offline mode, use <code>offline</code>.</p>
+<p>Bypasses staleness checks for cached searches. Missing data will still
+be requested from the server. To force full offline mode, use <code>offline</code>.</p>
<h4 id="offline">offline</h4>
<p>Forces full offline mode. Any searches not locally cached will result in
an error.</p>
diff --git a/deps/npm/docs/output/commands/npm-update.html b/deps/npm/docs/output/commands/npm-update.html
index 7533721fa3e..1c5d53e5d24 100644
--- a/deps/npm/docs/output/commands/npm-update.html
+++ b/deps/npm/docs/output/commands/npm-update.html
@@ -136,7 +136,7 @@ npm command-line interface
<section id="content">
<header class="title">
<h1 id="npm-update">npm-update</h1>
-<span class="description">Update a package</span>
+<span class="description">Update packages</span>
</header>
<section id="table_of_contents">
@@ -159,18 +159,10 @@ as well.</p>
packages.</p>
<p>If no package name is specified, all packages in the specified location (global
or local) will be updated.</p>
-<p>As of <code>npm@2.6.1</code>, the <code>npm update</code> will only inspect top-level packages.
-Prior versions of <code>npm</code> would also recursively inspect all dependencies.
-To get the old behavior, use <code>npm --depth 9999 update</code>.</p>
-<p>As of <code>npm@5.0.0</code>, the <code>npm update</code> will change <code>package.json</code> to save the
-new version as the minimum required dependency. To get the old behavior,
-use <code>npm update --no-save</code>.</p>
<h3 id="example">Example</h3>
-<p>IMPORTANT VERSION NOTE: these examples assume <code>npm@2.6.1</code> or later. For
-older versions of <code>npm</code>, you must specify <code>--depth 0</code> to get the behavior
-described below.</p>
<p>For the examples below, assume that the current package is <code>app</code> and it depends
-on dependencies, <code>dep1</code> (<code>dep2</code>, .. etc.). The published versions of <code>dep1</code> are:</p>
+on dependencies, <code>dep1</code> (<code>dep2</code>, .. etc.). The published versions of <code>dep1</code>
+are:</p>
<pre lang="json"><code>{
"dist-tags": { "latest": "1.2.2" },
"versions": [
@@ -200,10 +192,10 @@ on dependencies, <code>dep1</code> (<code>dep2</code>, .. etc.). The published
"dep1": "~1.1.1"
}
</code></pre>
-<p>In this case, running <code>npm update</code> will install <code>dep1@1.1.2</code>. Even though the <code>latest</code>
-tag points to <code>1.2.2</code>, this version does not satisfy <code>~1.1.1</code>, which is equivalent
-to <code>&gt;=1.1.1 &lt;1.2.0</code>. So the highest-sorting version that satisfies <code>~1.1.1</code> is used,
-which is <code>1.1.2</code>.</p>
+<p>In this case, running <code>npm update</code> will install <code>dep1@1.1.2</code>. Even though the
+<code>latest</code> tag points to <code>1.2.2</code>, this version do not satisfy <code>~1.1.1</code>, which is
+equivalent to <code>&gt;=1.1.1 &lt;1.2.0</code>. So the highest-sorting version that satisfies
+<code>~1.1.1</code> is used, which is <code>1.1.2</code>.</p>
<h4 id="caret-dependencies-below-100">Caret Dependencies below 1.0.0</h4>
<p>Suppose <code>app</code> has a caret dependency on a version below <code>1.0.0</code>, for example:</p>
<pre lang="json"><code>"dependencies": {
@@ -223,7 +215,9 @@ version that satisfies <code>^0.4.0</code> (<code>&gt;= 0.4.0 &lt;0.5.0</code>)<
<p><code>npm update -g</code> will apply the <code>update</code> action to each globally installed
package that is <code>outdated</code> – that is, has a version that is different from
<code>wanted</code>.</p>
-<p>Note: Globally installed packages are treated as if they are installed with a caret semver range specified. So if you require to update to <code>latest</code> you may need to run <code>npm install -g [&lt;pkg&gt;...]</code></p>
+<p>Note: Globally installed packages are treated as if they are installed with a
+caret semver range specified. So if you require to update to <code>latest</code> you may
+need to run <code>npm install -g [&lt;pkg&gt;...]</code></p>
<p>NOTE: If a package has been upgraded to a version newer than <code>latest</code>, it will
be <em>downgraded</em>.</p>
<h3 id="see-also">See Also</h3>
diff --git a/deps/npm/docs/output/commands/npm-version.html b/deps/npm/docs/output/commands/npm-version.html
index e11de2179b5..f5832a2d2fd 100644
--- a/deps/npm/docs/output/commands/npm-version.html
+++ b/deps/npm/docs/output/commands/npm-version.html
@@ -141,7 +141,7 @@ npm command-line interface
<section id="table_of_contents">
<h2 id="table-of-contents">Table of contents</h2>
-<div id="_table_of_contents"><ul><li><a href="#synopsis">Synopsis</a></li><li><a href="#description">Description</a></li><li><a href="#configuration">Configuration</a></li><ul><li><a href="#allow-same-version">allow-same-version</a></li><li><a href="#git-tag-version">git-tag-version</a></li><li><a href="#commit-hooks">commit-hooks</a></li><li><a href="#sign-git-tag">sign-git-tag</a></li></ul><li><a href="#see-also">See Also</a></li></ul></div>
+<div id="_table_of_contents"><ul><li><a href="#synopsis">Synopsis</a></li><li><a href="#description">Description</a></li><li><a href="#configuration">Configuration</a></li><ul><li><a href="#allow-same-version"><code>allow-same-version</code></a></li><li><a href="#git-tag-version"><code>git-tag-version</code></a></li><li><a href="#commit-hooks"><code>commit-hooks</code></a></li><li><a href="#sign-git-tag"><code>sign-git-tag</code></a></li></ul><li><a href="#see-also">See Also</a></li></ul></div>
</section>
<div id="_content"><h3 id="synopsis">Synopsis</h3>
@@ -207,32 +207,32 @@ the commit and/or tag.</li>
"postversion": "git push &amp;&amp; git push --tags &amp;&amp; rm -rf build/temp"
}
</code></pre>
-<p>This runs all your tests, and proceeds only if they pass. Then runs your <code>build</code> script, and
+<p>This runs all your tests and proceeds only if they pass. Then runs your <code>build</code> script, and
adds everything in the <code>dist</code> directory to the commit. After the commit, it pushes the new commit
and tag up to the server, and deletes the <code>build/temp</code> directory.</p>
<h3 id="configuration">Configuration</h3>
-<h4 id="allow-same-version">allow-same-version</h4>
+<h4 id="allow-same-version"><code>allow-same-version</code></h4>
<ul>
-<li>Default: false</li>
+<li>Default: <code>false</code></li>
<li>Type: Boolean</li>
</ul>
<p>Prevents throwing an error when <code>npm version</code> is used to set the new version
to the same value as the current version.</p>
-<h4 id="git-tag-version">git-tag-version</h4>
+<h4 id="git-tag-version"><code>git-tag-version</code></h4>
<ul>
-<li>Default: true</li>
+<li>Default: <code>true</code></li>
<li>Type: Boolean</li>
</ul>
<p>Commit and tag the version change.</p>
-<h4 id="commit-hooks">commit-hooks</h4>
+<h4 id="commit-hooks"><code>commit-hooks</code></h4>
<ul>
-<li>Default: true</li>
+<li>Default: <code>true</code></li>
<li>Type: Boolean</li>
</ul>
<p>Run git commit hooks when committing the version change.</p>
-<h4 id="sign-git-tag">sign-git-tag</h4>
+<h4 id="sign-git-tag"><code>sign-git-tag</code></h4>
<ul>
-<li>Default: false</li>
+<li>Default: <code>false</code></li>
<li>Type: Boolean</li>
</ul>
<p>Pass the <code>-s</code> flag to git to sign the tag.</p>
@@ -243,7 +243,6 @@ to the same value as the current version.</p>
<li><a href="../commands/npm-run-script.html">npm run-script</a></li>
<li><a href="../using-npm/scripts.html">npm scripts</a></li>
<li><a href="../configuring-npm/package-json.html">package.json</a></li>
-<li><a href="../using-npm/semver.html">semver</a></li>
<li><a href="../using-npm/config.html">config</a></li>
</ul>
</div>
diff --git a/deps/npm/docs/output/commands/npm-view.html b/deps/npm/docs/output/commands/npm-view.html
index 9865e5a8886..d7790e2fa7a 100644
--- a/deps/npm/docs/output/commands/npm-view.html
+++ b/deps/npm/docs/output/commands/npm-view.html
@@ -152,34 +152,32 @@ aliases: info, show, v
<h3 id="description">Description</h3>
<p>This command shows data about a package and prints it to the stream
referenced by the <code>outfd</code> config, which defaults to stdout.</p>
-<p>To show the package registry entry for the <code>connect</code> package, you can do
-this:</p>
+<p>As an example, to view information about the <code>connect</code> package from the registry, you would run:</p>
<pre lang="bash"><code>npm view connect
</code></pre>
-<p>The default version is “latest” if unspecified.</p>
+<p>The default version is <code>"latest"</code> if unspecified.</p>
<p>Field names can be specified after the package descriptor.
For example, to show the dependencies of the <code>ronn</code> package at version
-0.3.5, you could do the following:</p>
+<code>0.3.5</code>, you could do the following:</p>
<pre lang="bash"><code>npm view ronn@0.3.5 dependencies
</code></pre>
<p>You can view child fields by separating them with a period.
-To view the git repository URL for the latest version of npm, you could
-do this:</p>
+To view the git repository URL for the latest version of <code>npm</code>, you would run the following command:</p>
<pre lang="bash"><code>npm view npm repository.url
</code></pre>
<p>This makes it easy to view information about a dependency with a bit of
-shell scripting. For example, to view all the data about the version of
-opts that ronn depends on, you can do this:</p>
+shell scripting. For example, to view all the data about the version of
+<code>opts</code> that <code>ronn</code> depends on, you could write the following:</p>
<pre lang="bash"><code>npm view opts@$(npm view ronn dependencies.opts)
</code></pre>
<p>For fields that are arrays, requesting a non-numeric field will return
-all of the values from the objects in the list. For example, to get all
-the contributor names for the “express” project, you can do this:</p>
+all of the values from the objects in the list. For example, to get all
+the contributor names for the <code>express</code> package, you would run:</p>
<pre lang="bash"><code>npm view express contributors.email
</code></pre>
<p>You may also use numeric indices in square braces to specifically select
-an item in an array field. To just get the email address of the first
-contributor in the list, you can do this:</p>
+an item in an array field. To just get the email address of the first
+contributor in the list, you can run:</p>
<pre lang="bash"><code>npm view express contributors[0].email
</code></pre>
<p>Multiple fields may be specified, and will be printed one after another.
@@ -188,13 +186,13 @@ can do this:</p>
<pre lang="bash"><code>npm view express contributors.name contributors.email
</code></pre>
<p>“Person” fields are shown as a string if they would be shown as an
-object. So, for example, this will show the list of npm contributors in
+object. So, for example, this will show the list of <code>npm</code> contributors in
the shortened string format. (See <a href="../configuring-npm/package.json.html"><code>package.json</code></a> for more on this.)</p>
<pre lang="bash"><code>npm view npm contributors
</code></pre>
<p>If a version range is provided, then data will be printed for every
-matching version of the package. This will show which version of jsdom
-was required by each matching version of yui3:</p>
+matching version of the package. This will show which version of <code>jsdom</code>
+was required by each matching version of <code>yui3</code>:</p>
<pre lang="bash"><code>npm view yui3@'&gt;0.5.4' dependencies.jsdom
</code></pre>
<p>To show the <code>connect</code> package version history, you can do
@@ -203,12 +201,12 @@ this:</p>
</code></pre>
<h3 id="output">Output</h3>
<p>If only a single string field for a single version is output, then it
-will not be colorized or quoted, so as to enable piping the output to
+will not be colorized or quoted, to enable piping the output to
another command. If the field is an object, it will be output as a JavaScript object literal.</p>
-<p>If the –json flag is given, the outputted fields will be JSON.</p>
-<p>If the version range matches multiple versions, than each printed value
+<p>If the <code>--json</code> flag is given, the outputted fields will be JSON.</p>
+<p>If the version range matches multiple versions then each printed value
will be prefixed with the version it applies to.</p>
-<p>If multiple fields are requested, than each of them are prefixed with
+<p>If multiple fields are requested, then each of them is prefixed with
the field name.</p>
<h3 id="see-also">See Also</h3>
<ul>
diff --git a/deps/npm/docs/output/commands/npm.html b/deps/npm/docs/output/commands/npm.html
index 03d4c928210..5a7976ca0c8 100644
--- a/deps/npm/docs/output/commands/npm.html
+++ b/deps/npm/docs/output/commands/npm.html
@@ -148,31 +148,36 @@ npm command-line interface
<pre lang="bash"><code>npm &lt;command&gt; [args]
</code></pre>
<h3 id="version">Version</h3>
-<p>7.4.3</p>
+<p>7.5.0</p>
<h3 id="description">Description</h3>
<p>npm is the package manager for the Node JavaScript platform. It puts
modules in place so that node can find them, and manages dependency
conflicts intelligently.</p>
-<p>It is extremely configurable to support a wide variety of use cases.
-Most commonly, it is used to publish, discover, install, and develop node
+<p>It is extremely configurable to support a variety of use cases. Most
+commonly, you use it to publish, discover, install, and develop node
programs.</p>
<p>Run <code>npm help</code> to get a list of available commands.</p>
<h3 id="important">Important</h3>
-<p>npm is configured to use npm, Inc.’s public registry at
+<p>npm comes preconfigured to use npm’s public registry at
<a href="https://registry.npmjs.org">https://registry.npmjs.org</a> by default. Use of the npm public registry is
-subject to terms of use available at <a href="https://www.npmjs.com/policies/terms">https://www.npmjs.com/policies/terms</a>.</p>
-<p>You can configure npm to use any compatible registry you like, and even run
-your own registry. Use of someone else’s registry may be governed by their
-terms of use.</p>
+subject to terms of use available at
+<a href="https://www.npmjs.com/policies/terms">https://www.npmjs.com/policies/terms</a>.</p>
+<p>You can configure npm to use any compatible registry you like, and even
+run your own registry. Use of someone else’s registry is governed by
+their terms of use.</p>
<h3 id="introduction">Introduction</h3>
<p>You probably got npm because you want to install stuff.</p>
-<p>Use <code>npm install blerg</code> to install the latest version of “blerg”. Check out
-<a href="../commands/npm-install.html"><code>npm install</code></a> for more info. It can do a lot of stuff.</p>
-<p>Use the <code>npm search</code> command to show everything that’s available.
-Use <code>npm ls</code> to show everything you’ve installed.</p>
+<p>The very first thing you will most likely want to run in any node
+program is <code>npm install</code> to install its dependencies.</p>
+<p>You can also run <code>npm install blerg</code> to install the latest version of
+“blerg”. Check out <a href="../commands/npm-install.html"><code>npm install</code></a> for more
+info. It can do a lot of stuff.</p>
+<p>Use the <code>npm search</code> command to show everything that’s available in the
+public registry. Use <code>npm ls</code> to show everything you’ve installed.</p>
<h3 id="dependencies">Dependencies</h3>
-<p>If a package references to another package with a git URL, npm depends
-on a preinstalled git.</p>
+<p>If a package lists a dependency using a git URL, npm will install that
+dependency using the <a href="https://github.com/git-guides/install-git"><code>git</code></a>
+command and will generate an error if it is not installed.</p>
<p>If one of the packages npm tries to install is a native node module and
requires compiling of C++ Code, npm will use
<a href="https://github.com/nodejs/node-gyp">node-gyp</a> for that task.
@@ -184,38 +189,41 @@ For more information visit
<a href="https://github.com/nodejs/node-gyp">the node-gyp repository</a> and
the <a href="https://github.com/nodejs/node-gyp/wiki">node-gyp Wiki</a>.</p>
<h3 id="directories">Directories</h3>
-<p>See <a href="../configuring-npm/folders.html"><code>folders</code></a> to learn about where npm puts stuff.</p>
+<p>See <a href="../configuring-npm/folders.html"><code>folders</code></a> to learn about where npm puts
+stuff.</p>
<p>In particular, npm has two modes of operation:</p>
<ul>
-<li>global mode:
-npm installs packages into the install prefix at
-<code>prefix/lib/node_modules</code> and bins are installed in <code>prefix/bin</code>.</li>
<li>local mode:
npm installs packages into the current project directory, which
-defaults to the current working directory. Packages are installed to
-<code>./node_modules</code>, and bins are installed to <code>./node_modules/.bin</code>.</li>
+defaults to the current working directory. Packages install to
+<code>./node_modules</code>, and bins to <code>./node_modules/.bin</code>.</li>
+<li>global mode:
+npm installs packages into the install prefix at
+<code>$npm_config_prefix/lib/node_modules</code> and bins to
+<code>$npm_config_prefix/bin</code>.</li>
</ul>
<p>Local mode is the default. Use <code>-g</code> or <code>--global</code> on any command to
-operate in global mode instead.</p>
+run in global mode instead.</p>
<h3 id="developer-usage">Developer Usage</h3>
<p>If you’re using npm to develop and publish your code, check out the
following help topics:</p>
<ul>
<li>json:
-Make a package.json file. See <a href="../configuring-npm/package-json.html"><code>package.json</code></a>.</li>
+Make a package.json file. See
+<a href="../configuring-npm/package-json.html"><code>package.json</code></a>.</li>
<li>link:
-For linking your current working code into Node’s path, so that you
-don’t have to reinstall every time you make a change. Use
-<code>npm link</code> to do this.</li>
+Links your current working code into Node’s path, so that you don’t
+have to reinstall every time you make a change. Use <a href="../commands/npm-link.html"><code>npm link</code></a> to do this.</li>
<li>install:
-It’s a good idea to install things if you don’t need the symbolic link.
-Especially, installing other peoples code from the registry is done via
-<code>npm install</code></li>
+It’s a good idea to install things if you don’t need the symbolic
+link. Especially, installing other peoples code from the registry is
+done via <a href="../commands/npm-install.html"><code>npm install</code></a></li>
<li>adduser:
-Create an account or log in. Credentials are stored in the
-user config file.</li>
+Create an account or log in. When you do this, npm will store
+credentials in the user config file config file.</li>
<li>publish:
-Use the <code>npm publish</code> command to upload your code to the registry.</li>
+Use the <a href="../commands/npm-publish%60.html"><code>npm publish</code></a> command to upload your
+code to the registry.</li>
</ul>
<h4 id="configuration">Configuration</h4>
<p>npm is extremely configurable. It reads its configuration options from
@@ -224,20 +232,20 @@ Use the <code>npm publish</code> command to upload your code to the registry.</l
<li>Command line switches:
Set a config with <code>--key val</code>. All keys take a value, even if they
are booleans (the config parser doesn’t know what the options are at
-the time of parsing). If no value is provided, then the option is set
-to boolean <code>true</code>.</li>
+the time of parsing). If you do not provide a value (<code>--key</code>) then
+the option is set to boolean <code>true</code>.</li>
<li>Environment Variables:
Set any config by prefixing the name in an environment variable with
<code>npm_config_</code>. For example, <code>export npm_config_key=val</code>.</li>
<li>User Configs:
-The file at $HOME/.npmrc is an ini-formatted list of configs. If
+The file at <code>$HOME/.npmrc</code> is an ini-formatted list of configs. If
present, it is parsed. If the <code>userconfig</code> option is set in the cli
-or env, then that will be used instead.</li>
+or env, that file will be used instead.</li>
<li>Global Configs:
-The file found at ../etc/npmrc (from the node executable, by default
-this resolves to /usr/local/etc/npmrc) will be parsed if it is found.
-If the <code>globalconfig</code> option is set in the cli, env, or user config,
-then that file is parsed instead.</li>
+The file found at <code>./etc/npmrc</code> (relative to the global prefix will be
+parsed if it is found. See <a href="../commands/npm-prefix.html"><code>npm prefix</code></a> for
+more info on the global prefix. If the <code>globalconfig</code> option is set
+in the cli, env, or user config, then that file is parsed instead.</li>
<li>Defaults:
npm’s default configuration options are defined in
lib/utils/config-defs.js. These must not be changed.</li>
@@ -245,12 +253,14 @@ lib/utils/config-defs.js. These must not be changed.</li>
<p>See <a href="../using-npm/config.html"><code>config</code></a> for much much more information.</p>
<h3 id="contributions">Contributions</h3>
<p>Patches welcome!</p>
-<p>If you would like to contribute, but don’t know what to work on, read
-the <a href="https://github.com/npm/cli/blob/latest/CONTRIBUTING.md">contributing guidelines</a>
-and check the issues list.</p>
+<p>If you would like to help, but don’t know what to work on, read the
+<a href="https://github.com/npm/cli/blob/latest/CONTRIBUTING.md">contributing
+guidelines</a> and
+check the issues list.</p>
<h3 id="bugs">Bugs</h3>
-<p>When you find issues, please report them: <a href="https://github.com/npm/cli/issues">https://github.com/npm/cli/issues</a></p>
-<p>Be sure to follow the template and bug reporting guidelines.</p>
+<p>When you find issues, please report them:
+<a href="https://github.com/npm/cli/issues">https://github.com/npm/cli/issues</a></p>
+<p>Please be sure to follow the template and bug reporting guidelines.</p>
<h3 id="feature-requests">Feature Requests</h3>
<p>Discuss new feature ideas on our discussion forum:</p>
<ul>
@@ -264,9 +274,11 @@ and check the issues list.</p>
<ul>
<li><a href="../commands/npm-help.html">npm help</a></li>
<li><a href="../configuring-npm/package-json.html">package.json</a></li>
-<li><a href="../commands/npm-install.html">npm install</a></li>
-<li><a href="../commands/npm-config.html">npm config</a></li>
<li><a href="../configuring-npm/npmrc.html">npmrc</a></li>
+<li><a href="../commands/npm-config.html">npm config</a></li>
+<li><a href="../commands/npm-install.html">npm install</a></li>
+<li><a href="../commands/npm-prefix.html">npm prefix</a></li>
+<li><a href="../commands/npm-publish.html">npm publish</a></li>
</ul>
</div>
generated by cgit v1.2.3 (git 2.25.1) at 2024-08-04 10:32:17 +0300