diff options
Diffstat (limited to 'deps/npm/html/doc/misc')
| -rw-r--r-- | deps/npm/html/doc/misc/npm-coding-style.html | 6 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-config.html | 4 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-developers.html | 4 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-disputes.html | 14 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-index.html | 154 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-orgs.html | 2 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-registry.html | 14 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-scope.html | 2 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/npm-scripts.html | 6 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/removing-npm.html | 2 | ||||
| -rw-r--r-- | deps/npm/html/doc/misc/semver.html | 37 |
11 files changed, 129 insertions, 116 deletions
diff --git a/deps/npm/html/doc/misc/npm-coding-style.html b/deps/npm/html/doc/misc/npm-coding-style.html index 6005929dc4..3e4632d678 100644 --- a/deps/npm/html/doc/misc/npm-coding-style.html +++ b/deps/npm/html/doc/misc/npm-coding-style.html @@ -89,7 +89,7 @@ Also use a single space wherever it makes things more readable.</p> lines. Don't use more spaces than are helpful.</p> <h2 id="functions">Functions</h2> <p>Use named functions. They make stack traces a lot easier to read.</p> -<h2 id="callbacks-sync-async-style">Callbacks, Sync/async Style</h2> +<h2 id="callbacks-syncasync-style">Callbacks, Sync/async Style</h2> <p>Use the asynchronous/non-blocking versions of things as much as possible. It might make more sense for npm to use the synchronous fs APIs, but this way, the fs and http and child process stuff all uses the same callback-passing @@ -110,7 +110,7 @@ report what's happening so that it's easier to track down where a fault occurs.</p> <p>Use appropriate log levels. See <code><a href="../misc/npm-config.html">npm-config(7)</a></code> and search for "loglevel".</p> -<h2 id="case-naming-etc-">Case, naming, etc.</h2> +<h2 id="case-naming-etc">Case, naming, etc.</h2> <p>Use <code>lowerCamelCase</code> for multiword identifiers when they refer to objects, functions, methods, properties, or anything not specified in this section.</p> <p>Use <code>UpperCamelCase</code> for class names (things that you'd pass to "new").</p> @@ -145,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.5.0</p> +<p id="footer">npm-coding-style — npm@6.7.0</p> diff --git a/deps/npm/html/doc/misc/npm-config.html b/deps/npm/html/doc/misc/npm-config.html index 91af998a04..d09706648f 100644 --- a/deps/npm/html/doc/misc/npm-config.html +++ b/deps/npm/html/doc/misc/npm-config.html @@ -259,7 +259,7 @@ disabled when the environment variable <code>NO_COLOR</code> is set to any value since that gives more useful information. To show the outdated status of all packages and dependents, use a large integer value, e.g., <code>npm outdated --depth 9999</code></p> -<h3 id="description">description</h3> +<h3 id="description-1">description</h3> <ul> <li>Default: true</li> <li>Type: Boolean</li> @@ -1064,5 +1064,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.5.0</p> +<p id="footer">npm-config — npm@6.7.0</p> diff --git a/deps/npm/html/doc/misc/npm-developers.html b/deps/npm/html/doc/misc/npm-developers.html index 04b069a5cd..04c4430a51 100644 --- a/deps/npm/html/doc/misc/npm-developers.html +++ b/deps/npm/html/doc/misc/npm-developers.html @@ -41,7 +41,7 @@ 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 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> +<h2 id="the-packagejson-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 much of anything with npm. That is basically the whole interface.</p> <p>See <code><a href="../files/package.json.html">package.json(5)</a></code> for details about what goes in that file. At the very @@ -198,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.5.0</p> +<p id="footer">npm-developers — npm@6.7.0</p> diff --git a/deps/npm/html/doc/misc/npm-disputes.html b/deps/npm/html/doc/misc/npm-disputes.html index 617838f0cb..1bc5deee22 100644 --- a/deps/npm/html/doc/misc/npm-disputes.html +++ b/deps/npm/html/doc/misc/npm-disputes.html @@ -17,10 +17,10 @@ take about names you think infringe your trademarks.</p> <a href="https://www.npmjs.com/policies/conduct">npm Code of Conduct</a>, and nothing in this document should be interpreted to contradict any aspect of the npm Code of Conduct.</p> -<h2 id="tl-dr">TL;DR</h2> +<h2 id="tldr">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> @@ -58,13 +58,13 @@ because Yusuf's <code>foo</code> is in the way.</p> </li> <li><p>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.</p> </li> <li><p>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.)</p> </li> </ol> @@ -101,12 +101,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://www.npmjs.com/">https://www.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 @@ -139,5 +139,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.5.0</p> +<p id="footer">npm-disputes — npm@6.7.0</p> diff --git a/deps/npm/html/doc/misc/npm-index.html b/deps/npm/html/doc/misc/npm-index.html index 967162c3f2..5044c30449 100644 --- a/deps/npm/html/doc/misc/npm-index.html +++ b/deps/npm/html/doc/misc/npm-index.html @@ -10,163 +10,165 @@ <div id="wrapper"> <h1><a href="../misc/npm-index.html">npm-index</a></h1> <p>Index of all npm documentation</p> -<h3 id="readme-1-"><a href="../../doc/README.html">README</a></h3> +<h3 id="readme1"><a href="../../doc/README.html">README</a></h3> <p>a JavaScript package manager</p> <h2 id="command-line-documentation">Command Line Documentation</h2> <p>Using npm on the command line</p> -<h3 id="npm-1-"><a href="../cli/npm.html">npm(1)</a></h3> +<h3 id="npm1"><a href="../cli/npm.html">npm(1)</a></h3> <p>javascript package manager</p> -<h3 id="npm-access-1-"><a href="../cli/npm-access.html">npm-access(1)</a></h3> +<h3 id="npm-access1"><a href="../cli/npm-access.html">npm-access(1)</a></h3> <p>Set access level on published packages</p> -<h3 id="npm-adduser-1-"><a href="../cli/npm-adduser.html">npm-adduser(1)</a></h3> +<h3 id="npm-adduser1"><a href="../cli/npm-adduser.html">npm-adduser(1)</a></h3> <p>Add a registry user account</p> -<h3 id="npm-audit-1-"><a href="../cli/npm-audit.html">npm-audit(1)</a></h3> +<h3 id="npm-audit1"><a href="../cli/npm-audit.html">npm-audit(1)</a></h3> <p>Run a security audit</p> -<h3 id="npm-bin-1-"><a href="../cli/npm-bin.html">npm-bin(1)</a></h3> +<h3 id="npm-bin1"><a href="../cli/npm-bin.html">npm-bin(1)</a></h3> <p>Display npm bin folder</p> -<h3 id="npm-bugs-1-"><a href="../cli/npm-bugs.html">npm-bugs(1)</a></h3> +<h3 id="npm-bugs1"><a href="../cli/npm-bugs.html">npm-bugs(1)</a></h3> <p>Bugs for a package in a web browser maybe</p> -<h3 id="npm-build-1-"><a href="../cli/npm-build.html">npm-build(1)</a></h3> +<h3 id="npm-build1"><a href="../cli/npm-build.html">npm-build(1)</a></h3> <p>Build a package</p> -<h3 id="npm-bundle-1-"><a href="../cli/npm-bundle.html">npm-bundle(1)</a></h3> +<h3 id="npm-bundle1"><a href="../cli/npm-bundle.html">npm-bundle(1)</a></h3> <p>REMOVED</p> -<h3 id="npm-cache-1-"><a href="../cli/npm-cache.html">npm-cache(1)</a></h3> +<h3 id="npm-cache1"><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> +<h3 id="npm-ci1"><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> +<h3 id="npm-completion1"><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> +<h3 id="npm-config1"><a href="../cli/npm-config.html">npm-config(1)</a></h3> <p>Manage the npm configuration files</p> -<h3 id="npm-dedupe-1-"><a href="../cli/npm-dedupe.html">npm-dedupe(1)</a></h3> +<h3 id="npm-dedupe1"><a href="../cli/npm-dedupe.html">npm-dedupe(1)</a></h3> <p>Reduce duplication</p> -<h3 id="npm-deprecate-1-"><a href="../cli/npm-deprecate.html">npm-deprecate(1)</a></h3> +<h3 id="npm-deprecate1"><a href="../cli/npm-deprecate.html">npm-deprecate(1)</a></h3> <p>Deprecate a version of a package</p> -<h3 id="npm-dist-tag-1-"><a href="../cli/npm-dist-tag.html">npm-dist-tag(1)</a></h3> +<h3 id="npm-dist-tag1"><a href="../cli/npm-dist-tag.html">npm-dist-tag(1)</a></h3> <p>Modify package distribution tags</p> -<h3 id="npm-docs-1-"><a href="../cli/npm-docs.html">npm-docs(1)</a></h3> +<h3 id="npm-docs1"><a href="../cli/npm-docs.html">npm-docs(1)</a></h3> <p>Docs for a package in a web browser maybe</p> -<h3 id="npm-doctor-1-"><a href="../cli/npm-doctor.html">npm-doctor(1)</a></h3> +<h3 id="npm-doctor1"><a href="../cli/npm-doctor.html">npm-doctor(1)</a></h3> <p>Check your environments</p> -<h3 id="npm-edit-1-"><a href="../cli/npm-edit.html">npm-edit(1)</a></h3> +<h3 id="npm-edit1"><a href="../cli/npm-edit.html">npm-edit(1)</a></h3> <p>Edit an installed package</p> -<h3 id="npm-explore-1-"><a href="../cli/npm-explore.html">npm-explore(1)</a></h3> +<h3 id="npm-explore1"><a href="../cli/npm-explore.html">npm-explore(1)</a></h3> <p>Browse an installed package</p> -<h3 id="npm-help-search-1-"><a href="../cli/npm-help-search.html">npm-help-search(1)</a></h3> +<h3 id="npm-help-search1"><a href="../cli/npm-help-search.html">npm-help-search(1)</a></h3> <p>Search npm help documentation</p> -<h3 id="npm-help-1-"><a href="../cli/npm-help.html">npm-help(1)</a></h3> +<h3 id="npm-help1"><a href="../cli/npm-help.html">npm-help(1)</a></h3> <p>Get help on npm</p> -<h3 id="npm-hook-1-"><a href="../cli/npm-hook.html">npm-hook(1)</a></h3> +<h3 id="npm-hook1"><a href="../cli/npm-hook.html">npm-hook(1)</a></h3> <p>Manage registry hooks</p> -<h3 id="npm-init-1-"><a href="../cli/npm-init.html">npm-init(1)</a></h3> +<h3 id="npm-init1"><a href="../cli/npm-init.html">npm-init(1)</a></h3> <p>create a package.json file</p> -<h3 id="npm-install-ci-test-1-"><a href="../cli/npm-install-ci-test.html">npm-install-ci-test(1)</a></h3> +<h3 id="npm-install-ci-test1"><a href="../cli/npm-install-ci-test.html">npm-install-ci-test(1)</a></h3> <p>Install a project with a clean slate and run tests</p> -<h3 id="npm-install-test-1-"><a href="../cli/npm-install-test.html">npm-install-test(1)</a></h3> +<h3 id="npm-install-test1"><a href="../cli/npm-install-test.html">npm-install-test(1)</a></h3> <p>Install package(s) and run tests</p> -<h3 id="npm-install-1-"><a href="../cli/npm-install.html">npm-install(1)</a></h3> +<h3 id="npm-install1"><a href="../cli/npm-install.html">npm-install(1)</a></h3> <p>Install a package</p> -<h3 id="npm-link-1-"><a href="../cli/npm-link.html">npm-link(1)</a></h3> +<h3 id="npm-link1"><a href="../cli/npm-link.html">npm-link(1)</a></h3> <p>Symlink a package folder</p> -<h3 id="npm-logout-1-"><a href="../cli/npm-logout.html">npm-logout(1)</a></h3> +<h3 id="npm-logout1"><a href="../cli/npm-logout.html">npm-logout(1)</a></h3> <p>Log out of the registry</p> -<h3 id="npm-ls-1-"><a href="../cli/npm-ls.html">npm-ls(1)</a></h3> +<h3 id="npm-ls1"><a href="../cli/npm-ls.html">npm-ls(1)</a></h3> <p>List installed packages</p> -<h3 id="npm-outdated-1-"><a href="../cli/npm-outdated.html">npm-outdated(1)</a></h3> +<h3 id="npm-org1"><a href="../cli/npm-org.html">npm-org(1)</a></h3> +<p>Manage orgs</p> +<h3 id="npm-outdated1"><a href="../cli/npm-outdated.html">npm-outdated(1)</a></h3> <p>Check for outdated packages</p> -<h3 id="npm-owner-1-"><a href="../cli/npm-owner.html">npm-owner(1)</a></h3> +<h3 id="npm-owner1"><a href="../cli/npm-owner.html">npm-owner(1)</a></h3> <p>Manage package owners</p> -<h3 id="npm-pack-1-"><a href="../cli/npm-pack.html">npm-pack(1)</a></h3> +<h3 id="npm-pack1"><a href="../cli/npm-pack.html">npm-pack(1)</a></h3> <p>Create a tarball from a package</p> -<h3 id="npm-ping-1-"><a href="../cli/npm-ping.html">npm-ping(1)</a></h3> +<h3 id="npm-ping1"><a href="../cli/npm-ping.html">npm-ping(1)</a></h3> <p>Ping npm registry</p> -<h3 id="npm-prefix-1-"><a href="../cli/npm-prefix.html">npm-prefix(1)</a></h3> +<h3 id="npm-prefix1"><a href="../cli/npm-prefix.html">npm-prefix(1)</a></h3> <p>Display prefix</p> -<h3 id="npm-profile-1-"><a href="../cli/npm-profile.html">npm-profile(1)</a></h3> +<h3 id="npm-profile1"><a href="../cli/npm-profile.html">npm-profile(1)</a></h3> <p>Change settings on your registry profile</p> -<h3 id="npm-prune-1-"><a href="../cli/npm-prune.html">npm-prune(1)</a></h3> +<h3 id="npm-prune1"><a href="../cli/npm-prune.html">npm-prune(1)</a></h3> <p>Remove extraneous packages</p> -<h3 id="npm-publish-1-"><a href="../cli/npm-publish.html">npm-publish(1)</a></h3> +<h3 id="npm-publish1"><a href="../cli/npm-publish.html">npm-publish(1)</a></h3> <p>Publish a package</p> -<h3 id="npm-rebuild-1-"><a href="../cli/npm-rebuild.html">npm-rebuild(1)</a></h3> +<h3 id="npm-rebuild1"><a href="../cli/npm-rebuild.html">npm-rebuild(1)</a></h3> <p>Rebuild a package</p> -<h3 id="npm-repo-1-"><a href="../cli/npm-repo.html">npm-repo(1)</a></h3> +<h3 id="npm-repo1"><a href="../cli/npm-repo.html">npm-repo(1)</a></h3> <p>Open package repository page in the browser</p> -<h3 id="npm-restart-1-"><a href="../cli/npm-restart.html">npm-restart(1)</a></h3> +<h3 id="npm-restart1"><a href="../cli/npm-restart.html">npm-restart(1)</a></h3> <p>Restart a package</p> -<h3 id="npm-root-1-"><a href="../cli/npm-root.html">npm-root(1)</a></h3> +<h3 id="npm-root1"><a href="../cli/npm-root.html">npm-root(1)</a></h3> <p>Display npm root</p> -<h3 id="npm-run-script-1-"><a href="../cli/npm-run-script.html">npm-run-script(1)</a></h3> +<h3 id="npm-run-script1"><a href="../cli/npm-run-script.html">npm-run-script(1)</a></h3> <p>Run arbitrary package scripts</p> -<h3 id="npm-search-1-"><a href="../cli/npm-search.html">npm-search(1)</a></h3> +<h3 id="npm-search1"><a href="../cli/npm-search.html">npm-search(1)</a></h3> <p>Search for packages</p> -<h3 id="npm-shrinkwrap-1-"><a href="../cli/npm-shrinkwrap.html">npm-shrinkwrap(1)</a></h3> +<h3 id="npm-shrinkwrap1"><a href="../cli/npm-shrinkwrap.html">npm-shrinkwrap(1)</a></h3> <p>Lock down dependency versions for publication</p> -<h3 id="npm-star-1-"><a href="../cli/npm-star.html">npm-star(1)</a></h3> +<h3 id="npm-star1"><a href="../cli/npm-star.html">npm-star(1)</a></h3> <p>Mark your favorite packages</p> -<h3 id="npm-stars-1-"><a href="../cli/npm-stars.html">npm-stars(1)</a></h3> +<h3 id="npm-stars1"><a href="../cli/npm-stars.html">npm-stars(1)</a></h3> <p>View packages marked as favorites</p> -<h3 id="npm-start-1-"><a href="../cli/npm-start.html">npm-start(1)</a></h3> +<h3 id="npm-start1"><a href="../cli/npm-start.html">npm-start(1)</a></h3> <p>Start a package</p> -<h3 id="npm-stop-1-"><a href="../cli/npm-stop.html">npm-stop(1)</a></h3> +<h3 id="npm-stop1"><a href="../cli/npm-stop.html">npm-stop(1)</a></h3> <p>Stop a package</p> -<h3 id="npm-team-1-"><a href="../cli/npm-team.html">npm-team(1)</a></h3> +<h3 id="npm-team1"><a href="../cli/npm-team.html">npm-team(1)</a></h3> <p>Manage organization teams and team memberships</p> -<h3 id="npm-test-1-"><a href="../cli/npm-test.html">npm-test(1)</a></h3> +<h3 id="npm-test1"><a href="../cli/npm-test.html">npm-test(1)</a></h3> <p>Test a package</p> -<h3 id="npm-token-1-"><a href="../cli/npm-token.html">npm-token(1)</a></h3> +<h3 id="npm-token1"><a href="../cli/npm-token.html">npm-token(1)</a></h3> <p>Manage your authentication tokens</p> -<h3 id="npm-uninstall-1-"><a href="../cli/npm-uninstall.html">npm-uninstall(1)</a></h3> +<h3 id="npm-uninstall1"><a href="../cli/npm-uninstall.html">npm-uninstall(1)</a></h3> <p>Remove a package</p> -<h3 id="npm-unpublish-1-"><a href="../cli/npm-unpublish.html">npm-unpublish(1)</a></h3> +<h3 id="npm-unpublish1"><a href="../cli/npm-unpublish.html">npm-unpublish(1)</a></h3> <p>Remove a package from the registry</p> -<h3 id="npm-update-1-"><a href="../cli/npm-update.html">npm-update(1)</a></h3> +<h3 id="npm-update1"><a href="../cli/npm-update.html">npm-update(1)</a></h3> <p>Update a package</p> -<h3 id="npm-version-1-"><a href="../cli/npm-version.html">npm-version(1)</a></h3> +<h3 id="npm-version1"><a href="../cli/npm-version.html">npm-version(1)</a></h3> <p>Bump a package version</p> -<h3 id="npm-view-1-"><a href="../cli/npm-view.html">npm-view(1)</a></h3> +<h3 id="npm-view1"><a href="../cli/npm-view.html">npm-view(1)</a></h3> <p>View registry info</p> -<h3 id="npm-whoami-1-"><a href="../cli/npm-whoami.html">npm-whoami(1)</a></h3> +<h3 id="npm-whoami1"><a href="../cli/npm-whoami.html">npm-whoami(1)</a></h3> <p>Display npm username</p> <h2 id="api-documentation">API Documentation</h2> <p>Using npm in your Node programs</p> <h2 id="files">Files</h2> <p>File system structures npm uses</p> -<h3 id="npm-folders-5-"><a href="../files/npm-folders.html">npm-folders(5)</a></h3> +<h3 id="npm-folders5"><a href="../files/npm-folders.html">npm-folders(5)</a></h3> <p>Folder Structures Used by npm</p> -<h3 id="npm-package-locks-5-"><a href="../files/npm-package-locks.html">npm-package-locks(5)</a></h3> +<h3 id="npm-package-locks5"><a href="../files/npm-package-locks.html">npm-package-locks(5)</a></h3> <p>An explanation of npm lockfiles</p> -<h3 id="npm-shrinkwrap-json-5-"><a href="../files/npm-shrinkwrap.json.html">npm-shrinkwrap.json(5)</a></h3> +<h3 id="npm-shrinkwrapjson5"><a href="../files/npm-shrinkwrap.json.html">npm-shrinkwrap.json(5)</a></h3> <p>A publishable lockfile</p> -<h3 id="npmrc-5-"><a href="../files/npmrc.html">npmrc(5)</a></h3> +<h3 id="npmrc5"><a href="../files/npmrc.html">npmrc(5)</a></h3> <p>The npm config files</p> -<h3 id="package-lock-json-5-"><a href="../files/package-lock.json.html">package-lock.json(5)</a></h3> +<h3 id="package-lockjson5"><a href="../files/package-lock.json.html">package-lock.json(5)</a></h3> <p>A manifestation of the manifest</p> -<h3 id="package-json-5-"><a href="../files/package.json.html">package.json(5)</a></h3> +<h3 id="packagejson5"><a href="../files/package.json.html">package.json(5)</a></h3> <p>Specifics of npm's package.json handling</p> <h2 id="misc">Misc</h2> <p>Various other bits and bobs</p> -<h3 id="npm-coding-style-7-"><a href="../misc/npm-coding-style.html">npm-coding-style(7)</a></h3> +<h3 id="npm-coding-style7"><a href="../misc/npm-coding-style.html">npm-coding-style(7)</a></h3> <p>npm's "funny" coding style</p> -<h3 id="npm-config-7-"><a href="../misc/npm-config.html">npm-config(7)</a></h3> +<h3 id="npm-config7"><a href="../misc/npm-config.html">npm-config(7)</a></h3> <p>More than you probably want to know about npm configuration</p> -<h3 id="npm-developers-7-"><a href="../misc/npm-developers.html">npm-developers(7)</a></h3> +<h3 id="npm-developers7"><a href="../misc/npm-developers.html">npm-developers(7)</a></h3> <p>Developer Guide</p> -<h3 id="npm-disputes-7-"><a href="../misc/npm-disputes.html">npm-disputes(7)</a></h3> +<h3 id="npm-disputes7"><a href="../misc/npm-disputes.html">npm-disputes(7)</a></h3> <p>Handling Module Name Disputes</p> -<h3 id="npm-index-7-"><a href="../misc/npm-index.html">npm-index(7)</a></h3> +<h3 id="npm-index7"><a href="../misc/npm-index.html">npm-index(7)</a></h3> <p>Index of all npm documentation</p> -<h3 id="npm-orgs-7-"><a href="../misc/npm-orgs.html">npm-orgs(7)</a></h3> +<h3 id="npm-orgs7"><a href="../misc/npm-orgs.html">npm-orgs(7)</a></h3> <p>Working with Teams & Orgs</p> -<h3 id="npm-registry-7-"><a href="../misc/npm-registry.html">npm-registry(7)</a></h3> +<h3 id="npm-registry7"><a href="../misc/npm-registry.html">npm-registry(7)</a></h3> <p>The JavaScript Package Registry</p> -<h3 id="npm-scope-7-"><a href="../misc/npm-scope.html">npm-scope(7)</a></h3> +<h3 id="npm-scope7"><a href="../misc/npm-scope.html">npm-scope(7)</a></h3> <p>Scoped packages</p> -<h3 id="npm-scripts-7-"><a href="../misc/npm-scripts.html">npm-scripts(7)</a></h3> +<h3 id="npm-scripts7"><a href="../misc/npm-scripts.html">npm-scripts(7)</a></h3> <p>How npm handles the "scripts" field</p> -<h3 id="removing-npm-7-"><a href="../misc/removing-npm.html">removing-npm(7)</a></h3> +<h3 id="removing-npm7"><a href="../misc/removing-npm.html">removing-npm(7)</a></h3> <p>Cleaning the Slate</p> -<h3 id="semver-7-"><a href="../misc/semver.html">semver(7)</a></h3> +<h3 id="semver7"><a href="../misc/semver.html">semver(7)</a></h3> <p>The semantic versioner for npm</p> </div> @@ -180,5 +182,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.5.0</p> +<p id="footer">npm-index — npm@6.7.0</p> diff --git a/deps/npm/html/doc/misc/npm-orgs.html b/deps/npm/html/doc/misc/npm-orgs.html index d8194a94a3..75d23d6bea 100644 --- a/deps/npm/html/doc/misc/npm-orgs.html +++ b/deps/npm/html/doc/misc/npm-orgs.html @@ -77,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.5.0</p> +<p id="footer">npm-orgs — npm@6.7.0</p> diff --git a/deps/npm/html/doc/misc/npm-registry.html b/deps/npm/html/doc/misc/npm-registry.html index 16f8b7864c..ca2352a7ef 100644 --- a/deps/npm/html/doc/misc/npm-registry.html +++ b/deps/npm/html/doc/misc/npm-registry.html @@ -31,7 +31,7 @@ available at <a href="https://github.com/npm/npm-registry-couchapp">https://gith <code><a href="../misc/npm-scope.html">npm-scope(7)</a></code>). If no scope is specified, the default registry is used, which is supplied by the <code>registry</code> config parameter. See <code><a href="../cli/npm-config.html">npm-config(1)</a></code>, <code><a href="../files/npmrc.html">npmrc(5)</a></code>, and <code><a href="../misc/npm-config.html">npm-config(7)</a></code> for more on managing npm's configuration.</p> -<h2 id="does-npm-send-any-information-about-me-back-to-the-registry-">Does npm send any information about me back to the registry?</h2> +<h2 id="does-npm-send-any-information-about-me-back-to-the-registry">Does npm send any information about me back to the registry?</h2> <p>Yes.</p> <p>When making requests of the registry npm adds two headers with information about your environment:</p> @@ -51,7 +51,7 @@ build farms.</li> </ul> <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> +<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 similar) design doc to implement the APIs.</p> @@ -61,20 +61,20 @@ to read any published packages, in addition to your private ones, and by default will only publish internally. </p> <p>If you then want to publish a package for the whole world to see, you can simply override the <code>--registry</code> option for that <code>publish</code> command.</p> -<h2 id="i-don-t-want-my-package-published-in-the-official-registry-it-s-private-">I don't want my package published in the official registry. It's private.</h2> +<h2 id="i-dont-want-my-package-published-in-the-official-registry-its-private">I don't want my package published in the official registry. It's private.</h2> <p>Set <code>"private": true</code> in your package.json to prevent it from being published at all, or <code>"publishConfig":{"registry":"http://my-internal-registry.local"}</code> to force it to be published only to your internal registry.</p> <p>See <code><a href="../files/package.json.html">package.json(5)</a></code> for more info on what goes in the package.json file.</p> -<h2 id="will-you-replicate-from-my-registry-into-the-public-one-">Will you replicate from my registry into the public one?</h2> +<h2 id="will-you-replicate-from-my-registry-into-the-public-one">Will you replicate from my registry into the public one?</h2> <p>No. If you want things to be public, then publish them into the public registry using npm. What little security there is would be for nought otherwise.</p> -<h2 id="do-i-have-to-use-couchdb-to-build-a-registry-that-npm-can-talk-to-">Do I have to use couchdb to build a registry that npm can talk to?</h2> +<h2 id="do-i-have-to-use-couchdb-to-build-a-registry-that-npm-can-talk-to">Do I have to use couchdb to build a registry that npm can talk to?</h2> <p>No, but it's way easier. Basically, yes, you do, or you have to effectively implement the entire CouchDB API anyway.</p> -<h2 id="is-there-a-website-or-something-to-see-package-docs-and-such-">Is there a website or something to see package docs and such?</h2> +<h2 id="is-there-a-website-or-something-to-see-package-docs-and-such">Is there a website or something to see package docs and such?</h2> <p>Yes, head over to <a href="https://www.npmjs.com/">https://www.npmjs.com/</a></p> <h2 id="see-also">SEE ALSO</h2> <ul> @@ -96,5 +96,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.5.0</p> +<p id="footer">npm-registry — npm@6.7.0</p> diff --git a/deps/npm/html/doc/misc/npm-scope.html b/deps/npm/html/doc/misc/npm-scope.html index b6caab6caf..329812894e 100644 --- a/deps/npm/html/doc/misc/npm-scope.html +++ b/deps/npm/html/doc/misc/npm-scope.html @@ -93,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.5.0</p> +<p id="footer">npm-scope — npm@6.7.0</p> diff --git a/deps/npm/html/doc/misc/npm-scripts.html b/deps/npm/html/doc/misc/npm-scripts.html index bdce4134ae..1533d13b63 100644 --- a/deps/npm/html/doc/misc/npm-scripts.html +++ b/deps/npm/html/doc/misc/npm-scripts.html @@ -127,7 +127,7 @@ executing the scripts. So, if your package.json has this:</p> , "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 exported into the <code>node_modules/.bin</code> directory on <code>npm install</code>.</p> -<h3 id="package-json-vars">package.json vars</h3> +<h3 id="packagejson-vars">package.json vars</h3> <p>The package.json fields are tacked onto the <code>npm_package_</code> prefix. So, for instance, if you had <code>{"name":"foo", "version":"1.2.5"}</code> in your package.json file, then your package scripts would have the @@ -139,7 +139,7 @@ in your code with <code>process.env.npm_package_name</code> and <p>Configuration parameters are put in the environment with the <code>npm_config_</code> prefix. For instance, you can view the effective <code>root</code> config by checking the <code>npm_config_root</code> environment variable.</p> -<h3 id="special-package-json-config-object">Special: package.json "config" object</h3> +<h3 id="special-packagejson-config-object">Special: package.json "config" object</h3> <p>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> @@ -234,5 +234,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.5.0</p> +<p id="footer">npm-scripts — npm@6.7.0</p> diff --git a/deps/npm/html/doc/misc/removing-npm.html b/deps/npm/html/doc/misc/removing-npm.html index 830a5c5b79..d31c293c9d 100644 --- a/deps/npm/html/doc/misc/removing-npm.html +++ b/deps/npm/html/doc/misc/removing-npm.html @@ -52,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.5.0</p> +<p id="footer">removing-npm — npm@6.7.0</p> diff --git a/deps/npm/html/doc/misc/semver.html b/deps/npm/html/doc/misc/semver.html index a202644c53..28db44aa66 100644 --- a/deps/npm/html/doc/misc/semver.html +++ b/deps/npm/html/doc/misc/semver.html @@ -11,8 +11,7 @@ <h1><a href="../misc/semver.html">semver</a></h1> <p>The semantic versioner for npm</p> <h2 id="install">Install</h2> -<pre><code class="language-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="language-js">const semver = require('semver') @@ -28,8 +27,6 @@ semver.valid(semver.coerce('42.6.7.9.3-alpha')) // '42.6.7'</cod <p>As a command-line utility:</p> <pre><code>$ semver -h -SemVer 5.3.0 - A JavaScript implementation of the http://semver.org/ specification Copyright Isaac Z. Schlueter @@ -53,6 +50,9 @@ Options: -l --loose Interpret versions and ranges loosely +-p --include-prerelease + Always include prerelease versions in range matching + -c --coerce Coerce a string into SemVer if possible (does not imply --loose) @@ -133,7 +133,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-xyz---abc">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> @@ -151,7 +151,7 @@ provided tuple parts.</p> <li><code>1.2.3 - 2.3</code> := <code>>=1.2.3 <2.4.0</code></li> <li><code>1.2.3 - 2</code> := <code>>=1.2.3 <3.0.0</code></li> </ul> -<h4 id="x-ranges-1-2-x-1-x-1-2-">X-Ranges <code>1.2.x</code> <code>1.X</code> <code>1.2.*</code> <code>*</code></h4> +<h4 id="x-ranges-12x-1x-12-">X-Ranges <code>1.2.x</code> <code>1.X</code> <code>1.2.*</code> <code>*</code></h4> <p>Any of <code>X</code>, <code>x</code>, or <code>*</code> may be used to "stand in" for one of the numeric values in the <code>[major, minor, patch]</code> tuple.</p> <ul> @@ -166,7 +166,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-123-12-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 +182,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-123-025-004">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 @@ -242,9 +242,20 @@ build ::= parts parts ::= part ( '.' part ) * 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. -The resulting output will always be 100% strict, of course.</p> +<p>All methods and classes take a final <code>options</code> object argument. All +options in this object are <code>false</code> by default. The options supported +are:</p> +<ul> +<li><code>loose</code> Be more forgiving about not-quite-valid semver strings. +(Any resulting output will always be 100% strict compliant, of +course.) For backwards compatibility reasons, if the <code>options</code> +argument is a boolean value instead of an object, it is interpreted +to be the <code>loose</code> param.</li> +<li><code>includePrerelease</code> Set to suppress the <a href="https://github.com/npm/node-semver#prerelease-tags">default +behavior</a> of +excluding prerelease tagged versions from ranges unless they are +explicitly opted into.</li> +</ul> <p>Strict-mode Comparators and Ranges will be strict about the SemVer strings that they parse.</p> <ul> @@ -295,7 +306,7 @@ or null if the versions are the same.</li> <ul> <li><code>intersects(comparator)</code>: Return true if the comparators intersect</li> </ul> -<h3 id="ranges">Ranges</h3> +<h3 id="ranges-1">Ranges</h3> <ul> <li><code>validRange(range)</code>: Return the valid range or null if it's not valid</li> <li><code>satisfies(version, range)</code>: Return true if the version satisfies the @@ -350,5 +361,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.5.0</p> +<p id="footer">semver — npm@6.7.0</p> |