summaryrefslogtreecommitdiff
path: root/deps/npm/html/doc/files
diff options
context:
space:
mode:
authorKat Marchán <kzm@zkat.tech>2018-08-29 12:03:09 -0700
committerMichaël Zasso <targos@protonmail.com>2018-09-06 08:53:57 +0200
commit6d6db603e299b2df82fd1d451b83de60c60fc082 (patch)
treed2c69476aeef34282e4c866461be0440d31b3f73 /deps/npm/html/doc/files
parentcab8a0bd924c5ac2bbbdf971631f057960f084e4 (diff)
downloadnode-new-6d6db603e299b2df82fd1d451b83de60c60fc082.tar.gz
deps: upgrade npm to 6.4.1
PR-URL: https://github.com/nodejs/node/pull/22591 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Diffstat (limited to 'deps/npm/html/doc/files')
-rw-r--r--deps/npm/html/doc/files/npm-folders.html2
-rw-r--r--deps/npm/html/doc/files/npm-global.html2
-rw-r--r--deps/npm/html/doc/files/npm-json.html22
-rw-r--r--deps/npm/html/doc/files/npm-package-locks.html2
-rw-r--r--deps/npm/html/doc/files/npm-shrinkwrap.json.html2
-rw-r--r--deps/npm/html/doc/files/npmrc.html2
-rw-r--r--deps/npm/html/doc/files/package-lock.json.html2
-rw-r--r--deps/npm/html/doc/files/package.json.html22
8 files changed, 28 insertions, 28 deletions
diff --git a/deps/npm/html/doc/files/npm-folders.html b/deps/npm/html/doc/files/npm-folders.html
index 4a9942d7ab..95285eead0 100644
--- a/deps/npm/html/doc/files/npm-folders.html
+++ b/deps/npm/html/doc/files/npm-folders.html
@@ -179,5 +179,5 @@ cannot be found elsewhere. See <code><a href="../files/package.json.html">packa
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
-<p id="footer">npm-folders &mdash; npm@6.2.0</p>
+<p id="footer">npm-folders &mdash; npm@6.4.1</p>
diff --git a/deps/npm/html/doc/files/npm-global.html b/deps/npm/html/doc/files/npm-global.html
index 4a9942d7ab..95285eead0 100644
--- a/deps/npm/html/doc/files/npm-global.html
+++ b/deps/npm/html/doc/files/npm-global.html
@@ -179,5 +179,5 @@ cannot be found elsewhere. See <code><a href="../files/package.json.html">packa
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
-<p id="footer">npm-folders &mdash; npm@6.2.0</p>
+<p id="footer">npm-folders &mdash; npm@6.4.1</p>
diff --git a/deps/npm/html/doc/files/npm-json.html b/deps/npm/html/doc/files/npm-json.html
index 0edcca4702..5d9a0f79b6 100644
--- a/deps/npm/html/doc/files/npm-json.html
+++ b/deps/npm/html/doc/files/npm-json.html
@@ -81,7 +81,7 @@ current SPDX license identifier for the license you&#39;re using, like this:</p>
<pre><code>{ &quot;license&quot; : &quot;BSD-3-Clause&quot; }</code></pre><p>You can check <a href="https://spdx.org/licenses/">the full list of SPDX license IDs</a>.
Ideally you should pick one that is
<a href="https://opensource.org/licenses/alphabetical">OSI</a> approved.</p>
-<p>If your package is licensed under multiple common licenses, use an <a href="https://npmjs.com/package/spdx">SPDX license
+<p>If your package is licensed under multiple common licenses, use an <a href="https://www.npmjs.com/package/spdx">SPDX license
expression syntax version 2.0 string</a>, like this:</p>
<pre><code>{ &quot;license&quot; : &quot;(ISC OR GPL-3.0)&quot; }</code></pre><p>If you are using a license that hasn&#39;t been assigned an SPDX identifier, or if
you are using a custom license, use a string value like this one:</p>
@@ -256,15 +256,15 @@ future.</p>
want to contribute. If the git repo is on GitHub, then the <code>npm docs</code>
command will be able to find you.</p>
<p>Do it like this:</p>
-<pre><code>&quot;repository&quot; :
- { &quot;type&quot; : &quot;git&quot;
- , &quot;url&quot; : &quot;https://github.com/npm/cli.git&quot;
- }
+<pre><code>&quot;repository&quot;: {
+ &quot;type&quot; : &quot;git&quot;,
+ &quot;url&quot; : &quot;https://github.com/npm/cli.git&quot;
+}
-&quot;repository&quot; :
- { &quot;type&quot; : &quot;svn&quot;
- , &quot;url&quot; : &quot;https://v8.googlecode.com/svn/trunk/&quot;
- }</code></pre><p>The URL should be a publicly available (perhaps read-only) url that can be handed
+&quot;repository&quot;: {
+ &quot;type&quot; : &quot;svn&quot;,
+ &quot;url&quot; : &quot;https://v8.googlecode.com/svn/trunk/&quot;
+}</code></pre><p>The URL should be a publicly available (perhaps read-only) url that can be handed
directly to a VCS program without any modification. It should not be a url to an
html project page that you put in your browser. It&#39;s for computers.</p>
<p>For GitHub, GitHub gist, Bitbucket, or GitLab repositories you can use the same
@@ -434,7 +434,7 @@ dependency hell, a situation that npm is designed to avoid as much as possible.<
<p>Trying to install another plugin with a conflicting requirement will cause an
error. For this reason, make sure your plugin requirement is as broad as
possible, and not to lock it down to specific patch versions.</p>
-<p>Assuming the host complies with <a href="http://semver.org/">semver</a>, only changes in
+<p>Assuming the host complies with <a href="https://semver.org/">semver</a>, only changes in
the host package&#39;s major version will break your plugin. Thus, if you&#39;ve worked
with every 1.x version of the host package, use <code>&quot;^1.0&quot;</code> or <code>&quot;1.x&quot;</code> to express
this. If you depend on features introduced in 1.5.2, use <code>&quot;&gt;= 1.5.2 &lt; 2&quot;</code>.</p>
@@ -574,5 +574,5 @@ ignored.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
-<p id="footer">package.json &mdash; npm@6.2.0</p>
+<p id="footer">package.json &mdash; npm@6.4.1</p>
diff --git a/deps/npm/html/doc/files/npm-package-locks.html b/deps/npm/html/doc/files/npm-package-locks.html
index 50ac0d4db8..425d274eb7 100644
--- a/deps/npm/html/doc/files/npm-package-locks.html
+++ b/deps/npm/html/doc/files/npm-package-locks.html
@@ -151,4 +151,4 @@ npm-merge-driver install -g</code> will let you do this, and even works with
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
-<p id="footer">npm-package-locks &mdash; npm@6.2.0</p>
+<p id="footer">npm-package-locks &mdash; npm@6.4.1</p>
diff --git a/deps/npm/html/doc/files/npm-shrinkwrap.json.html b/deps/npm/html/doc/files/npm-shrinkwrap.json.html
index 66cd483cb4..0d01fdf56b 100644
--- a/deps/npm/html/doc/files/npm-shrinkwrap.json.html
+++ b/deps/npm/html/doc/files/npm-shrinkwrap.json.html
@@ -42,4 +42,4 @@ to the manual page for <a href="../files/package-lock.json.html">package-lock.js
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
-<p id="footer">npm-shrinkwrap.json &mdash; npm@6.2.0</p>
+<p id="footer">npm-shrinkwrap.json &mdash; npm@6.4.1</p>
diff --git a/deps/npm/html/doc/files/npmrc.html b/deps/npm/html/doc/files/npmrc.html
index bdb87a2019..eb83450634 100644
--- a/deps/npm/html/doc/files/npmrc.html
+++ b/deps/npm/html/doc/files/npmrc.html
@@ -82,5 +82,5 @@ manner.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
-<p id="footer">npmrc &mdash; npm@6.2.0</p>
+<p id="footer">npmrc &mdash; npm@6.4.1</p>
diff --git a/deps/npm/html/doc/files/package-lock.json.html b/deps/npm/html/doc/files/package-lock.json.html
index 82ccc40dc0..5732969d25 100644
--- a/deps/npm/html/doc/files/package-lock.json.html
+++ b/deps/npm/html/doc/files/package-lock.json.html
@@ -130,4 +130,4 @@ should match via normal matching rules a dependency either in our
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
-<p id="footer">package-lock.json &mdash; npm@6.2.0</p>
+<p id="footer">package-lock.json &mdash; npm@6.4.1</p>
diff --git a/deps/npm/html/doc/files/package.json.html b/deps/npm/html/doc/files/package.json.html
index 0edcca4702..5d9a0f79b6 100644
--- a/deps/npm/html/doc/files/package.json.html
+++ b/deps/npm/html/doc/files/package.json.html
@@ -81,7 +81,7 @@ current SPDX license identifier for the license you&#39;re using, like this:</p>
<pre><code>{ &quot;license&quot; : &quot;BSD-3-Clause&quot; }</code></pre><p>You can check <a href="https://spdx.org/licenses/">the full list of SPDX license IDs</a>.
Ideally you should pick one that is
<a href="https://opensource.org/licenses/alphabetical">OSI</a> approved.</p>
-<p>If your package is licensed under multiple common licenses, use an <a href="https://npmjs.com/package/spdx">SPDX license
+<p>If your package is licensed under multiple common licenses, use an <a href="https://www.npmjs.com/package/spdx">SPDX license
expression syntax version 2.0 string</a>, like this:</p>
<pre><code>{ &quot;license&quot; : &quot;(ISC OR GPL-3.0)&quot; }</code></pre><p>If you are using a license that hasn&#39;t been assigned an SPDX identifier, or if
you are using a custom license, use a string value like this one:</p>
@@ -256,15 +256,15 @@ future.</p>
want to contribute. If the git repo is on GitHub, then the <code>npm docs</code>
command will be able to find you.</p>
<p>Do it like this:</p>
-<pre><code>&quot;repository&quot; :
- { &quot;type&quot; : &quot;git&quot;
- , &quot;url&quot; : &quot;https://github.com/npm/cli.git&quot;
- }
+<pre><code>&quot;repository&quot;: {
+ &quot;type&quot; : &quot;git&quot;,
+ &quot;url&quot; : &quot;https://github.com/npm/cli.git&quot;
+}
-&quot;repository&quot; :
- { &quot;type&quot; : &quot;svn&quot;
- , &quot;url&quot; : &quot;https://v8.googlecode.com/svn/trunk/&quot;
- }</code></pre><p>The URL should be a publicly available (perhaps read-only) url that can be handed
+&quot;repository&quot;: {
+ &quot;type&quot; : &quot;svn&quot;,
+ &quot;url&quot; : &quot;https://v8.googlecode.com/svn/trunk/&quot;
+}</code></pre><p>The URL should be a publicly available (perhaps read-only) url that can be handed
directly to a VCS program without any modification. It should not be a url to an
html project page that you put in your browser. It&#39;s for computers.</p>
<p>For GitHub, GitHub gist, Bitbucket, or GitLab repositories you can use the same
@@ -434,7 +434,7 @@ dependency hell, a situation that npm is designed to avoid as much as possible.<
<p>Trying to install another plugin with a conflicting requirement will cause an
error. For this reason, make sure your plugin requirement is as broad as
possible, and not to lock it down to specific patch versions.</p>
-<p>Assuming the host complies with <a href="http://semver.org/">semver</a>, only changes in
+<p>Assuming the host complies with <a href="https://semver.org/">semver</a>, only changes in
the host package&#39;s major version will break your plugin. Thus, if you&#39;ve worked
with every 1.x version of the host package, use <code>&quot;^1.0&quot;</code> or <code>&quot;1.x&quot;</code> to express
this. If you depend on features introduced in 1.5.2, use <code>&quot;&gt;= 1.5.2 &lt; 2&quot;</code>.</p>
@@ -574,5 +574,5 @@ ignored.</p>
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6>&nbsp;</td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)">&nbsp;</td></tr>
<tr><td colspan=5 style="width:50px;height:10px;background:#fff">&nbsp;</td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4>&nbsp;</td><td style="width:90px;height:10px;background:#fff" colspan=9>&nbsp;</td></tr>
</table>
-<p id="footer">package.json &mdash; npm@6.2.0</p>
+<p id="footer">package.json &mdash; npm@6.4.1</p>