diff options
| author | FallenRiteMonk <fallenritemonk@gmail.com> | 2018-04-05 18:52:34 +0300 |
|---|---|---|
| committer | Myles Borins <mylesborins@google.com> | 2018-04-05 23:01:07 +0300 |
| commit | 25a816dcda7b1db0929501acfe13f2fe5119759b (patch) | |
| tree | d3df4377a11dfb643b5976d2048d9bb4ee527903 /deps/npm/html/doc/misc | |
| parent | b29c36b80746733994257b7380245102bc3c4cd6 (diff) | |
deps: upgrade npm to 5.8.0
PR-URL: https://github.com/nodejs/node/pull/19560
Fixes: https://github.com/nodejs/node/issues/19271
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Myles Borins <myles.borins@gmail.com>
Diffstat (limited to 'deps/npm/html/doc/misc')
| -rw-r--r-- | deps/npm/html/doc/misc/npm-coding-style.html | 4 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-config.html | 19 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-developers.html | 6 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-disputes.html | 14 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-index.html | 4 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-orgs.html | 2 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-registry.html | 2 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-scope.html | 2 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-scripts.html | 16 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/removing-npm.html | 2 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/semver.html | 29 |
11 files changed, 67 insertions, 33 deletions
diff --git a/deps/npm/html/doc/misc/npm-coding-style.html b/deps/npm/html/doc/misc/npm-coding-style.html index f96dd270bfa..a5a446d7a96 100644 --- a/deps/npm/html/doc/misc/npm-coding-style.html +++ b/deps/npm/html/doc/misc/npm-coding-style.html @@ -91,7 +91,7 @@ final token in the list on a line by itself. For example:</p> <pre><code>var ok = 'String contains "double" quotes' var alsoOk = "String contains 'single' quotes or apostrophe" </code></pre><h2 id="whitespace">Whitespace</h2> -<p>Put a single space in front of ( for anything other than a function call. +<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 lines. Don't use more spaces than are helpful.</p> @@ -153,5 +153,5 @@ set to anything."</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-coding-style — npm@5.6.0</p> +<p id="footer">npm-coding-style — npm@5.8.0</p> diff --git a/deps/npm/html/doc/misc/npm-config.html b/deps/npm/html/doc/misc/npm-config.html index a23b10727af..f191df813a2 100644 --- a/deps/npm/html/doc/misc/npm-config.html +++ b/deps/npm/html/doc/misc/npm-config.html @@ -239,6 +239,8 @@ PEM format (Windows calls it "Base-64 encoded X.509 (.CER)") with newl </ul> <p>If false, never shows colors. If <code>"always"</code> then always shows colors. If true, then only prints color codes for tty file descriptors.</p> +<p>This option can also be changed using the environment: colors are +disabled when the environment variable <code>NO_COLOR</code> is set to any value.</p> <h3 id="depth">depth</h3> <ul> <li>Default: Infinity</li> @@ -560,7 +562,7 @@ combination). Passed to the <code>http</code> <code>Agent</code> used to make th <p>Any "%s" in the message will be replaced with the version number.</p> <h3 id="metrics-registry">metrics-registry</h3> <ul> -<li>Default: The value of <code>registry</code> (which defaults to "<a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a>")</li> +<li>Default: The value of <code>registry</code> (which defaults to "<a href="https://registry.npmjs.org/"">https://registry.npmjs.org/"</a>)</li> <li>Type: String</li> </ul> <p>The registry you want to send cli metrics to if <code>send-metrics</code> is true.</p> @@ -578,6 +580,12 @@ impact how lifecycle scripts are called.</p> <li>Type: semver or false</li> </ul> <p>The node version to use when checking a package's <code>engines</code> map.</p> +<h3 id="no-proxy">no-proxy</h3> +<ul> +<li>Default: null</li> +<li>Type: String or Array</li> +</ul> +<p>A comma-separated string or an array of domain extensions that a proxy should not be used for.</p> <h3 id="offline">offline</h3> <ul> <li>Default: false</li> @@ -628,13 +636,16 @@ when publishing or changing package permissions with <code>npm access</code>.</p </ul> <p>If set to false, then ignore <code>package-lock.json</code> files when installing. This will also prevent <em>writing</em> <code>package-lock.json</code> if <code>save</code> is true.</p> +<p>When package package-locks are disabled, automatic pruning of extraneous +modules will also be disabled. To remove extraneous modules with +package-locks disabled use <code>npm prune</code>.</p> <p>This option is an alias for <code>--shrinkwrap</code>.</p> <h3 id="package-lock-only">package-lock-only</h3> <ul> <li>Default: false</li> <li>Type: Boolean</li> </ul> -<p>If set to true, it will update only the <code>package-json</code>, +<p>If set to true, it will update only the <code>package-lock.json</code>, instead of checking <code>node_modules</code> and downloading dependencies.</p> <h3 id="parseable">parseable</h3> <ul> @@ -718,7 +729,7 @@ honored by the underlying <code>request</code> library.</p> <p>Remove failed installs.</p> <h3 id="save">save</h3> <ul> -<li>Default: false</li> +<li>Default: true</li> <li>Type: Boolean</li> </ul> <p>Save installed packages to a package.json file as dependencies.</p> @@ -1024,5 +1035,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@5.6.0</p> +<p id="footer">npm-config — npm@5.8.0</p> diff --git a/deps/npm/html/doc/misc/npm-developers.html b/deps/npm/html/doc/misc/npm-developers.html index bdf212ed4b1..b88c2020a03 100644 --- a/deps/npm/html/doc/misc/npm-developers.html +++ b/deps/npm/html/doc/misc/npm-developers.html @@ -20,7 +20,7 @@ that your users will do to install your program.</p> <p>These are man pages. If you install npm, you should be able to then do <code>man npm-thing</code> to get the documentation on a particular topic, or <code>npm help thing</code> to see the same information.</p> -<h2 id="what-is-a-package-">What is a <code>package</code></h2> +<h2 id="what-is-a-package">What is a <code>package</code></h2> <p>A package is:</p> <ul> <li>a) a folder containing a program described by a package.json file</li> @@ -53,7 +53,7 @@ This should be a string that identifies your project. Please do not use the name to specify that it runs on node, or is in JavaScript. You can use the "engines" field to explicitly state the versions of node (or whatever else) that your program requires, and it's pretty -well assumed that it's javascript.</p> +well assumed that it's JavaScript.</p> <p>It does not necessarily need to match your github repository name.</p> <p>So, <code>node-foo</code> and <code>bar-js</code> are bad names. <code>foo</code> or <code>bar</code> are better.</p> </li> @@ -204,5 +204,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@5.6.0</p> +<p id="footer">npm-developers — npm@5.8.0</p> diff --git a/deps/npm/html/doc/misc/npm-disputes.html b/deps/npm/html/doc/misc/npm-disputes.html index fdf53fcad0c..517ebfc33af 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`` is some different thing.</li> +<code>npm install</code>foo<code></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 @@ -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@5.6.0</p> +<p id="footer">npm-disputes — npm@5.8.0</p> diff --git a/deps/npm/html/doc/misc/npm-index.html b/deps/npm/html/doc/misc/npm-index.html index 927748e176c..03d8909267f 100644 --- a/deps/npm/html/doc/misc/npm-index.html +++ b/deps/npm/html/doc/misc/npm-index.html @@ -30,6 +30,8 @@ <p>REMOVED</p> <h3 id="npm-cache-1-"><a href="../cli/npm-cache.html">npm-cache(1)</a></h3> <p>Manipulates packages cache</p> +<h3 id="npm-ci-1-"><a href="../cli/npm-ci.html">npm-ci(1)</a></h3> +<p>Install a project with a clean slate</p> <h3 id="npm-completion-1-"><a href="../cli/npm-completion.html">npm-completion(1)</a></h3> <p>Tab Completion for npm</p> <h3 id="npm-config-1-"><a href="../cli/npm-config.html">npm-config(1)</a></h3> @@ -172,5 +174,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@5.6.0</p> +<p id="footer">npm-index — npm@5.8.0</p> diff --git a/deps/npm/html/doc/misc/npm-orgs.html b/deps/npm/html/doc/misc/npm-orgs.html index 5a11a10ca81..3ff8b5e6e85 100644 --- a/deps/npm/html/doc/misc/npm-orgs.html +++ b/deps/npm/html/doc/misc/npm-orgs.html @@ -86,5 +86,5 @@ <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">npm-orgs — npm@5.6.0</p> +<p id="footer">npm-orgs — npm@5.8.0</p> diff --git a/deps/npm/html/doc/misc/npm-registry.html b/deps/npm/html/doc/misc/npm-registry.html index cfa610d0e8d..beb59f87ae5 100644 --- a/deps/npm/html/doc/misc/npm-registry.html +++ b/deps/npm/html/doc/misc/npm-registry.html @@ -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@5.6.0</p> +<p id="footer">npm-registry — npm@5.8.0</p> diff --git a/deps/npm/html/doc/misc/npm-scope.html b/deps/npm/html/doc/misc/npm-scope.html index e610f3e9e36..997749d734b 100644 --- a/deps/npm/html/doc/misc/npm-scope.html +++ b/deps/npm/html/doc/misc/npm-scope.html @@ -99,5 +99,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@5.6.0</p> +<p id="footer">npm-scope — npm@5.8.0</p> diff --git a/deps/npm/html/doc/misc/npm-scripts.html b/deps/npm/html/doc/misc/npm-scripts.html index bc43c028f10..57468301cac 100644 --- a/deps/npm/html/doc/misc/npm-scripts.html +++ b/deps/npm/html/doc/misc/npm-scripts.html @@ -64,15 +64,15 @@ names will be run for those as well (e.g. <code>premyscript</code>, <code>myscri <p><pkg> -- npm run <stage>`.</p> <h2 id="prepublish-and-prepare">PREPUBLISH AND PREPARE</h2> <h3 id="deprecation-note">DEPRECATION NOTE</h3> -<p>Since <code>npm@1.1.71</code>, the npm CLI has run the <code>prepublish</code> script for both <code>npm -publish</code> and <code>npm install</code>, because it's a convenient way to prepare a package +<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 +publish<code>and</code>npm install<code>, because it's a convenient way to prepare a package for use (some common use cases are described in the section below). It has -also turned out to be, in practice, <a href="https://github.com/npm/npm/issues/10074">very -confusing</a>. As of <code>npm@4.0.0</code>, a new -event has been introduced, <code>prepare</code>, that preserves this existing behavior. A -<em>new</em> event, <code>prepublishOnly</code> has been added as a transitional strategy to +also turned out to be, in practice, [very +confusing](https://github.com/npm/npm/issues/10074). As of</code><a href="mailto:npm@4.0.0">npm@4.0.0</a><code>, a new +event has been introduced,</code>prepare<code>, that preserves this existing behavior. A +_new_ event,</code>prepublishOnly<code>has been added as a transitional strategy to allow users to avoid the confusing behavior of existing npm versions and only -run on <code>npm publish</code> (for instance, running the tests one last time to ensure +run on</code>npm publish` (for instance, running the tests one last time to ensure they're in good shape).</p> <p>See <a href="https://github.com/npm/npm/issues/10074">https://github.com/npm/npm/issues/10074</a> for a much lengthier justification, with further reading, for this change.</p> @@ -239,5 +239,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@5.6.0</p> +<p id="footer">npm-scripts — npm@5.8.0</p> diff --git a/deps/npm/html/doc/misc/removing-npm.html b/deps/npm/html/doc/misc/removing-npm.html index 1727455c627..9db0d76f514 100644 --- a/deps/npm/html/doc/misc/removing-npm.html +++ b/deps/npm/html/doc/misc/removing-npm.html @@ -57,5 +57,5 @@ modules. To track those down, you can do the following:</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">removing-npm — npm@5.6.0</p> +<p id="footer">removing-npm — npm@5.8.0</p> diff --git a/deps/npm/html/doc/misc/semver.html b/deps/npm/html/doc/misc/semver.html index afe72d30999..a4648065940 100644 --- a/deps/npm/html/doc/misc/semver.html +++ b/deps/npm/html/doc/misc/semver.html @@ -24,6 +24,8 @@ semver.clean(' =v1.2.3 ') // '1.2.3' semver.satisfies('1.2.3', '1.x || >=2.5.0 || 5.0.0 - 7.2.3') // true 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> <p>As a command-line utility:</p> <pre><code>$ semver -h @@ -53,6 +55,10 @@ Options: -l --loose Interpret versions and ranges loosely +-c --coerce + Coerce a string into SemVer if possible + (does not imply --loose) + Program exits successfully if any valid version satisfies all supplied ranges, and prints all satisfying versions. @@ -133,7 +139,7 @@ will append the value of the string as a prerelease identifier:</p> deterministic ways.</p> <p>Advanced ranges may be combined in the same way as primitive comparators using white space or <code>||</code>.</p> -<h4 id="hyphen-ranges-x-y-z-a-b-c-">Hyphen Ranges <code>X.Y.Z - A.B.C</code></h4> +<h4 id="hyphen-ranges-x-y-z-a-b-c">Hyphen Ranges <code>X.Y.Z - A.B.C</code></h4> <p>Specifies an inclusive set.</p> <ul> <li><code>1.2.3 - 2.3.4</code> := <code>>=1.2.3 <=2.3.4</code></li> @@ -166,7 +172,7 @@ character is in fact optional.</p> <li><code>1</code> := <code>1.x.x</code> := <code>>=1.0.0 <2.0.0</code></li> <li><code>1.2</code> := <code>1.2.x</code> := <code>>=1.2.0 <1.3.0</code></li> </ul> -<h4 id="tilde-ranges-1-2-3-1-2-1-">Tilde Ranges <code>~1.2.3</code> <code>~1.2</code> <code>~1</code></h4> +<h4 id="tilde-ranges-1-2-3-1-2-1">Tilde Ranges <code>~1.2.3</code> <code>~1.2</code> <code>~1</code></h4> <p>Allows patch-level changes if a minor version is specified on the comparator. Allows minor-level changes if not.</p> <ul> @@ -182,7 +188,7 @@ equal to <code>beta.2</code>. So, <code>1.2.3-beta.4</code> would be allowed, b <code>1.2.4-beta.2</code> would not, because it is a prerelease of a different <code>[major, minor, patch]</code> tuple.</li> </ul> -<h4 id="caret-ranges-1-2-3-0-2-5-0-0-4-">Caret Ranges <code>^1.2.3</code> <code>^0.2.5</code> <code>^0.0.4</code></h4> +<h4 id="caret-ranges-1-2-3-0-2-5-0-0-4">Caret Ranges <code>^1.2.3</code> <code>^0.2.5</code> <code>^0.0.4</code></h4> <p>Allows changes that do not modify the left-most non-zero digit in the <code>[major, minor, patch]</code> tuple. In other words, this allows patch and minor updates for versions <code>1.0.0</code> and above, patch updates for @@ -324,6 +330,21 @@ range (since <code>1.2.8</code> satisfies, which is lower), and it also does not satisfy the range.</p> <p>If you want to know if a version satisfies or does not satisfy a range, use the <code>satisfies(version, range)</code> function.</p> +<h3 id="coercion">Coercion</h3> +<ul> +<li><code>coerce(version)</code>: Coerces a string to semver if possible</li> +</ul> +<p>This aims to provide a very forgiving translation of a non-semver +string to semver. It looks for the first digit in a string, and +consumes all remaining characters which satisfy at least a partial semver +(e.g., <code>1</code>, <code>1.2</code>, <code>1.2.3</code>) up to the max permitted length (256 characters). +Longer versions are simply truncated (<code>4.6.3.9.2-alpha2</code> becomes <code>4.6.3</code>). +All surrounding text is simply ignored (<code>v3.4 replaces v3.3.1</code> becomes <code>3.4.0</code>). +Only text which lacks digits will fail coercion (<code>version one</code> is not valid). +The maximum length for any semver component considered for coercion is 16 characters; +longer components will be ignored (<code>10000000000000000.4.7.4</code> becomes <code>4.7.4</code>). +The maximum value for any semver component is <code>Integer.MAX_SAFE_INTEGER || (2**53 - 1)</code>; +higher value components are invalid (<code>9999999999999999.4.7.4</code> is likely invalid).</p> </div> @@ -336,5 +357,5 @@ range, use the <code>satisfies(version, range)</code> function.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">semver — npm@5.6.0</p> +<p id="footer">semver — npm@5.8.0</p> |