step-node-agent 3.20.2 → 3.21.0

package/node_modules/npm/docs/content/{cli-commands → commands}/npm-version.md

@@ -1,13 +1,9 @@
 ---
-section: cli-commands 
 title: npm-version
+section: 1
 description: Bump a package version
 ---
 
-# npm-version(1)
-
-## Bump a package version
-
 ### Synopsis
 
 ```bash
@@ -126,8 +122,8 @@ Note that you must have a default GPG key set up in your git config for this to
 
 ### See Also
 
-* [npm init](/cli-commands/npm-init)
-* [npm run-script](/cli-commands/npm-run-script)
+* [npm init](/commands/npm-init)
+* [npm run-script](/commands/npm-run-script)
 * [npm scripts](/using-npm/scripts)
 * [package.json](/configuring-npm/package-json)
 * [semver](/using-npm/semver)

package/node_modules/npm/docs/content/{cli-commands → commands}/npm-view.md

@@ -1,13 +1,9 @@
 ---
-section: cli-commands 
 title: npm-view
+section: 1
 description: View registry info
 ---
 
-# npm-view(1)
-
-## View registry info
-
 ### Synopsis
 
 ```bash
@@ -80,7 +76,7 @@ npm view express contributors.name contributors.email
 
 "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
-the shortened string format.  (See [`package.json`](/configuring-npm/package.json) for more on this.)
+the shortened string format.  (See [`package.json`](/configuring-npm/package-json) for more on this.)
 
 ```bash
 npm view npm contributors
@@ -117,8 +113,8 @@ the field name.
 
 ### See Also
 
-* [npm search](/cli-commands/npm-search)
+* [npm search](/commands/npm-search)
 * [npm registry](/using-npm/registry)
-* [npm config](/cli-commands/npm-config)
+* [npm config](/commands/npm-config)
 * [npmrc](/configuring-npm/npmrc)
-* [npm docs](/cli-commands/npm-docs)
+* [npm docs](/commands/npm-docs)

package/node_modules/npm/docs/content/{cli-commands → commands}/npm-whoami.md

@@ -1,12 +1,9 @@
 ---
-section: cli-commands 
 title: npm-whoami
+section: 1
 description: Display npm username
 ---
 
-# npm-whoami(1)
-## Display npm username
-
 ### Synopsis
 
 ```bash
@@ -19,6 +16,6 @@ Print the `username` config to standard output.
 
 ### See Also
 
-* [npm config](/cli-commands/npm-config)
+* [npm config](/commands/npm-config)
 * [npmrc](/configuring-npm/npmrc)
-* [npm adduser](/cli-commands/npm-adduser)
+* [npm adduser](/commands/npm-adduser)

package/node_modules/npm/docs/content/{cli-commands → commands}/npm.md

@@ -1,13 +1,9 @@
 ---
-section: cli-commands 
 title: npm
+section: 1
 description: javascript package manager
 ---
 
-# npm(1)
-
-## javascript package manager
-
 ### Synopsis
 
 ```bash
@@ -45,7 +41,7 @@ terms of use.
 You probably got npm because you want to install stuff.
 
 Use `npm install blerg` to install the latest version of "blerg".  Check out
-[`npm install`](/cli-commands/npm-install) for more info.  It can do a lot of stuff.
+[`npm install`](/commands/npm-install) for more info.  It can do a lot of stuff.
 
 Use the `npm search` command to show everything that's available.
 Use `npm ls` to show everything you've installed.
@@ -88,7 +84,7 @@ If you're using npm to develop and publish your code, check out the
 following help topics:
 
 * json:
-  Make a package.json file.  See [`package.json`](/configuring-npm/package.json).
+  Make a package.json file.  See [`package.json`](/configuring-npm/package-json).
 * 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
@@ -161,8 +157,8 @@ reproduction to report.
 <i@izs.me>
 
 ### See Also
-* [npm help](/cli-commands/npm-help)
+* [npm help](/commands/npm-help)
 * [package.json](/configuring-npm/package-json)
-* [npm install](/cli-commands/npm-install)
-* [npm config](/cli-commands/npm-config)
+* [npm install](/commands/npm-install)
+* [npm config](/commands/npm-config)
 * [npmrc](/configuring-npm/npmrc)

package/node_modules/npm/docs/content/configuring-npm/folders.md

@@ -1,13 +1,9 @@
 ---
-section: configuring-npm
 title: folders
+section: 5
 description: Folder Structures Used by npm
 ---
 
-# folders(5)
-
-## Folder Structures Used by npm
-
 ### Description
 
 npm puts various things on your computer.  That's its job.
@@ -73,7 +69,7 @@ Man pages are not installed on Windows systems.
 
 #### Cache
 
-See [`npm cache`](/cli-commands/npm-cache).  Cache files are stored in `~/.npm` on Posix, or
+See [`npm cache`](/commands/npm-cache).  Cache files are stored in `~/.npm` on Posix, or
 `%AppData%/npm-cache` on Windows.
 
 This is controlled by the `cache` configuration param.
@@ -209,15 +205,15 @@ not be included in the package tarball.
 
 This allows a package maintainer to install all of their dependencies
 (and dev dependencies) locally, but only re-publish those items that
-cannot be found elsewhere.  See [`package.json`](/configuring-npm/package.json) for more information.
+cannot be found elsewhere.  See [`package.json`](/configuring-npm/package-json) for more information.
 
 ### See also
 
 * [package.json](/configuring-npm/package-json)
-* [npm install](/cli-commands/npm-install)
-* [npm pack](/cli-commands/npm-pack)
-* [npm cache](/cli-commands/npm-cache)
-* [npm config](/cli-commands/npm-config)
+* [npm install](/commands/npm-install)
+* [npm pack](/commands/npm-pack)
+* [npm cache](/commands/npm-cache)
+* [npm config](/commands/npm-config)
 * [npmrc](/configuring-npm/npmrc)
 * [config](/using-npm/config)
-* [npm publish](/cli-commands/npm-publish)
+* [npm publish](/commands/npm-publish)

package/node_modules/npm/docs/content/configuring-npm/install.md

@@ -1,13 +1,9 @@
 ---
-section: configuring-npm
 title: install
+section: 5
 description: Download and install node and npm
 ---
 
-# install(5)
-
-## Download and Install npm
-
 ### Description
 
 To publish and install packages to and from the public npm registry, you must install Node.js and the npm command line interface using either a Node version manager or a Node installer. **We strongly recommend using a Node version manager to install Node.js and npm.** We do not recommend using a Node installer, since the Node installation process installs npm in a directory with local permissions and can cause permissions errors when you run npm packages globally.

package/node_modules/npm/docs/content/configuring-npm/npmrc.md

@@ -1,13 +1,9 @@
 ---
-section: configuring-npm
 title: npmrc
+section: 5
 description: The npm config files
 ---
 
-# npmrc(5)
-
-## The npm config files
-
 ### Description
 
 npm gets its config settings from the command line, environment
@@ -97,7 +93,7 @@ manner.
 ### See also
 
 * [npm folders](/configuring-npm/folders)
-* [npm config](/cli-commands/npm-config)
+* [npm config](/commands/npm-config)
 * [config](/using-npm/config)
 * [package.json](/configuring-npm/package-json)
-* [npm](/cli-commands/npm)
+* [npm](/commands/npm)

package/node_modules/npm/docs/content/configuring-npm/package-json.md

@@ -1,13 +1,9 @@
 ---
-section: configuring-npm
 title: package.json
+section: 5
 description: Specifics of npm's package.json handling
 ---
 
-# package.json(5)
-
-## Specifics of npm's package.json handling
-
 ### Description
 
 This document is all you need to know about what's required in your package.json
@@ -531,7 +527,7 @@ See [semver](/using-npm/semver) for more details about specifying version ranges
 * `range1 || range2` Passes if either range1 or range2 are satisfied.
 * `git...` See 'Git URLs as Dependencies' below
 * `user/repo` See 'GitHub URLs' below
-* `tag` A specific version tagged and published as `tag`  See [`npm dist-tag`](/cli-commands/npm-dist-tag)
+* `tag` A specific version tagged and published as `tag`  See [`npm dist-tag`](/commands/npm-dist-tag)
 * `path/path/path` See [Local Paths](#local-paths) below
 
 For example, these are all valid:
@@ -908,10 +904,10 @@ npm will default some values based on package contents.
 ### SEE ALSO
 
 * [semver](/using-npm/semver)
-* [npm init](/cli-commands/npm-init)
-* [npm version](/cli-commands/npm-version)
-* [npm config](/cli-commands/npm-config)
-* [npm help](/cli-commands/npm-help)
-* [npm install](/cli-commands/npm-install)
-* [npm publish](/cli-commands/npm-publish)
-* [npm uninstall](/cli-commands/npm-uninstall)
+* [npm init](/commands/npm-init)
+* [npm version](/commands/npm-version)
+* [npm config](/commands/npm-config)
+* [npm help](/commands/npm-help)
+* [npm install](/commands/npm-install)
+* [npm publish](/commands/npm-publish)
+* [npm uninstall](/commands/npm-uninstall)

package/node_modules/npm/docs/content/configuring-npm/package-lock-json.md

@@ -1,13 +1,9 @@
 ---
-section: configuring-npm
 title: package-lock.json
+section: 5
 description: A manifestation of the manifest
 ---
 
-# package-lock.json(5)
-
-## A manifestation of the manifest
-
 ### Description
 
 `package-lock.json` is automatically generated for any operations where npm
@@ -142,8 +138,8 @@ The dependencies of this dependency, exactly as at the top level.
 
 ### See also
 
-* [npm shrinkwrap](/cli-commands/npm-shrinkwrap)
+* [npm shrinkwrap](/commands/npm-shrinkwrap)
 * [shrinkwrap.json](/configuring-npm/shrinkwrap-json)
 * [package-locks](/configuring-npm/package-locks)
 * [package.json](/configuring-npm/package-json)
-* [npm install](/cli-commands/npm-install)
+* [npm install](/commands/npm-install)

package/node_modules/npm/docs/content/configuring-npm/package-locks.md

@@ -1,16 +1,12 @@
 ---
-section: configuring-npm
 title: package-locks
+section: 5
 description: An explanation of npm lockfiles
 ---
 
-# package-locks(5)
-
-## An explanation of npm lockfiles
-
 ### Description
 
-Conceptually, the "input" to [`npm install`](/cli-commands/npm-install) is a [package.json](/configuring-npm/package-json), while its
+Conceptually, the "input" to [`npm install`](/commands/npm-install) is a [package.json](/configuring-npm/package-json), while its
 "output" is a fully-formed `node_modules` tree: a representation of the
 dependencies you declared. In an ideal world, npm would work like a pure
 function: the same `package.json` should produce the exact same `node_modules`
@@ -179,4 +175,4 @@ pre-`npm@5.7.0` versions of npm 5, albeit a bit more noisily. Note that if
 * [package.json](/configuring-npm/package-json)
 * [package-lock.json](/configuring-npm/package-lock-json)
 * [shrinkwrap.json](/configuring-npm/shrinkwrap-json)
-* [npm shrinkwrap](/cli-commands/npm-shrinkwrap)
+* [npm shrinkwrap](/commands/npm-shrinkwrap)

package/node_modules/npm/docs/content/configuring-npm/shrinkwrap-json.md

@@ -1,16 +1,12 @@
 ---
-section: configuring-npm
 title: shrinkwrap.json
+section: 5
 description: A publishable lockfile
 ---
 
-# npm-shrinkwrap.json(5)
-
-## A publishable lockfile
-
 ### Description
 
-`npm-shrinkwrap.json` is a file created by [`npm shrinkwrap`](/cli-commands/npm-shrinkwrap). It is identical to
+`npm-shrinkwrap.json` is a file created by [`npm shrinkwrap`](/commands/npm-shrinkwrap). It is identical to
 `package-lock.json`, with one major caveat: Unlike `package-lock.json`,
 `npm-shrinkwrap.json` may be included when publishing a package.
 
@@ -28,7 +24,7 @@ to the manual page for [package-lock.json](/configuring-npm/package-lock-json).
 
 ### See also
 
-* [npm shrinkwrap](/cli-commands/npm-shrinkwrap)
+* [npm shrinkwrap](/commands/npm-shrinkwrap)
 * [package-lock.json](/configuring-npm/package-lock-json)
 * [package.json](/configuring-npm/package-json)
-* [npm install](/cli-commands/npm-install)
+* [npm install](/commands/npm-install)

package/node_modules/npm/docs/content/using-npm/config.md

@@ -1,13 +1,9 @@
 ---
-section: using-npm
 title: config
+section: 7
 description: More than you probably want to know about npm configuration
 ---
 
-# config(7)
-
-## More than you probably want to know about npm configuration
-
 ### Description
 
 npm gets its configuration values from the following sources, sorted by priority:
@@ -179,7 +175,7 @@ When "dev" or "development" and running local `npm shrinkwrap`,
 
 When "true" submit audit reports alongside `npm install` runs to the default
 registry and all registries configured for scopes.  See the documentation
-for [`npm audit`](/cli-commands/npm-audit) for details on what is submitted.
+for [`npm audit`](/commands/npm-audit) for details on what is submitted.
 
 #### audit-level
 
@@ -270,7 +266,7 @@ well as for the CA information to be stored in a file on disk.
 * Default: Windows: `%AppData%\npm-cache`, Posix: `~/.npm`
 * Type: path
 
-The location of npm's cache directory.  See [`npm cache`](/cli-commands/npm-cache)
+The location of npm's cache directory.  See [`npm cache`](/commands/npm-cache)
 
 #### cache-lock-stale
 
@@ -456,7 +452,7 @@ packages.
 
 When "true" displays the message at the end of each `npm install`
 acknowledging the number of dependencies looking for funding.
-See [`npm fund`](/cli-commands/npm-fund) for details.
+See [`npm fund`](/commands/npm-fund) for details.
 
 #### git
 
@@ -571,7 +567,7 @@ If true, npm does not run scripts specified in package.json files.
 A module that will be loaded by the `npm init` command.  See the
 documentation for the
 [init-package-json](https://github.com/isaacs/init-package-json) module
-for more information, or [npm init](/cli-commands/npm-init).
+for more information, or [npm init](/commands/npm-init).
 
 #### init-author-name
 
@@ -1228,7 +1224,7 @@ version of npm than the latest.
 * Type: Boolean
 
 Set to show short usage output (like the -H output)
-instead of complete help when doing [`npm help`](/cli-commands/npm-help).
+instead of complete help when doing [`npm help`](/commands/npm-help).
 
 #### user
 
@@ -1293,8 +1289,8 @@ Set to `"browser"` to view html help content in the default web browser.
 
 ### See also
 
-* [npm config](/cli-commands/npm-config)
+* [npm config](/commands/npm-config)
 * [npmrc](/configuring-npm/npmrc)
 * [npm scripts](/using-npm/scripts)
 * [npm folders](/configuring-npm/folders)
-* [npm](/cli-commands/npm)
+* [npm](/commands/npm)

package/node_modules/npm/docs/content/using-npm/developers.md

@@ -1,13 +1,9 @@
 ---
-section: using-npm
 title: developers
+section: 7
 description: Developer Guide
 ---
 
-# developers(7)
-
-## Developer Guide
-
 ### Description
 
 So, you've decided to use npm to develop (and maybe publish/deploy)
@@ -100,7 +96,7 @@ least, you need:
   they'll get installed just like these ones.
 
 You can use `npm init` in the root of your package in order to get you
-started with a pretty basic package.json file.  See [`npm init`](/cli-commands/npm-init) for
+started with a pretty basic package.json file.  See [`npm init`](/commands/npm-init) for
 more info.
 
 ### Keeping files *out* of your package
@@ -169,7 +165,7 @@ changes in real time without having to keep re-installing it.  (You do
 need to either re-link or `npm rebuild -g` to update compiled packages,
 of course.)
 
-More info at [`npm link`](/cli-commands/npm-link).
+More info at [`npm link`](/commands/npm-link).
 
 ### Before Publishing: Make Sure Your Package Installs and Works
 
@@ -217,7 +213,7 @@ npm adduser
 
 and then follow the prompts.
 
-This is documented better in [npm adduser](/cli-commands/npm-adduser).
+This is documented better in [npm adduser](/commands/npm-adduser).
 
 ### Publish your package
 
@@ -243,10 +239,10 @@ Tell the world how easy it is to install your program!
 
 ### See also
 
-* [npm](/cli-commands/npm)
-* [npm init](/cli-commands/npm-init)
+* [npm](/commands/npm)
+* [npm init](/commands/npm-init)
 * [package.json](/configuring-npm/package-json)
 * [npm scripts](/using-npm/scripts)
-* [npm publish](/cli-commands/npm-publish)
-* [npm adduser](/cli-commands/npm-adduser)
+* [npm publish](/commands/npm-publish)
+* [npm adduser](/commands/npm-adduser)
 * [npm registry](/using-npm/registry)

package/node_modules/npm/docs/content/using-npm/orgs.md

@@ -1,13 +1,9 @@
 ---
-section: using-npm
 title: orgs
+section: 7
 description: Working with Teams & Orgs
 ---
 
-# orgs(7)
-
-## Working with Teams & Orgs
-
 ### Description
 
 There are three levels of org users:
@@ -24,8 +20,8 @@ The developer will be able to access packages based on the teams they are on. Ac
 
 There are two main commands:
 
-1. `npm team` see [npm team](/cli-commands/npm-team) for more details
-2. `npm access` see [npm access](/cli-commands/npm-access) for more details
+1. `npm team` see [npm team](/commands/npm-team) for more details
+2. `npm access` see [npm access](/commands/npm-access) for more details
 
 ### Team Admins create teams
 
@@ -92,6 +88,6 @@ npm access ls-collaborators <pkg>
 
 ### See also
 
-* [npm team](/cli-commands/npm-team)
-* [npm access](/cli-commands/npm-access)
+* [npm team](/commands/npm-team)
+* [npm access](/commands/npm-access)
 * [npm scope](/using-npm/scope)

package/node_modules/npm/docs/content/using-npm/registry.md

@@ -1,13 +1,9 @@
 ---
-section: using-npm
 title: registry
+section: 7
 description: The JavaScript Package Registry
 ---
 
-# registry(7)
-
-##  The JavaScript Package Registry
-
 ### Description
 
 To resolve packages by name and version, npm talks to a registry website
@@ -33,7 +29,7 @@ available at <https://github.com/npm/npm-registry-couchapp>.
 
 The registry URL used is determined by the scope of the package (see
 [`scope`](/using-npm/scope). If no scope is specified, the default registry is used, which is
-supplied by the `registry` config parameter.  See [`npm config`](/cli-commands/npm-config),
+supplied by the `registry` config parameter.  See [`npm config`](/commands/npm-config),
 [`npmrc`](/configuring-npm/npmrc), and [`config`](/using-npm/config) for more on managing npm's configuration.
 
 ### Does npm send any information about me back to the registry?
@@ -100,8 +96,7 @@ Yes, head over to <https://www.npmjs.com/>
 
 ### See also
 
-* [npm config](/cli-commands/npm-config)
+* [npm config](/commands/npm-config)
 * [config](/using-npm/config)
 * [npmrc](/configuring-npm/npmrc)
 * [npm developers](/using-npm/developers)
-* [npm disputes](/using-npm/disputes)

package/node_modules/npm/docs/content/using-npm/removal.md

@@ -1,13 +1,9 @@
 ---
-section: using-npm
 title: removal
+section: 7
 description: Cleaning the Slate
 ---
 
-# removal(7)
-
-## Cleaning the Slate
-
 ### Synopsis
 
 So sad to see you go.
@@ -66,5 +62,5 @@ find /usr/local/{lib/node,bin} -exec grep -l npm \{\} \; ;
 
 ### See also
 
-* [npm uninstall](/cli-commands/npm-uninstall)
-* [npm prune](/cli-commands/npm-prune)
+* [npm uninstall](/commands/npm-uninstall)
+* [npm prune](/commands/npm-prune)

package/node_modules/npm/docs/content/using-npm/scope.md

@@ -1,11 +1,8 @@
 ---
-section: using-npm
 title: scope
+section: 7
 description: Scoped packages
 ---
-# scope(7)
-
-## Scoped packages
 
 ### Description
 
@@ -55,7 +52,7 @@ Or in `package.json`:
 ```
 
 Note that if the `@` symbol is omitted, in either case, npm will instead attempt to
-install from GitHub; see [`npm install`](/cli-commands/npm-install).
+install from GitHub; see [`npm install`](/commands/npm-install).
 
 ### Requiring scoped packages
 
@@ -101,7 +98,8 @@ desired, with `npm access` or on the npmjs.com website.
 
 Scopes can be associated with a separate registry. This allows you to
 seamlessly use a mix of packages from the primary npm registry and one or more
-private registries, such as npm Enterprise.
+private registries, such as GitHub Packages or the open source Verdaccio
+project.
 
 You can associate a scope with a registry at login, e.g.
 
@@ -125,7 +123,7 @@ that registry instead.
 
 ### See also
 
-* [npm install](/cli-commands/npm-install)
-* [npm publish](/cli-commands/npm-publish)
-* [npm access](/cli-commands/npm-access)
+* [npm install](/commands/npm-install)
+* [npm publish](/commands/npm-publish)
+* [npm access](/commands/npm-access)
 * [npm registry](/using-npm/registry)

package/node_modules/npm/docs/content/using-npm/scripts.md

@@ -1,13 +1,9 @@
 ---
-section: using-npm
 title: scripts
+section: 7
 description: How npm handles the "scripts" field
 ---
 
-# scripts(7)
-
-## How npm handles the "scripts" field
-
 ### Description
 
 The `"scripts"` property of of your `package.json` file supports a number of built-in scripts and their preset life cycle events as well as arbitrary scripts. These all can be executed by running `npm run-script <stage>` or `npm run <stage>` for short. *Pre* and *post* commands with matching names will be run for those as well (e.g. `premyscript`, `myscript`, `postmyscript`). Scripts from dependencies can be run with `npm explore <pkg> -- npm run <stage>`.
@@ -78,7 +74,7 @@ The advantage of doing these things at `prepublish` time is that they can be don
 
 ### Life Cycle Operation Order
 
-#### [`npm publish`](/cli-commands/npm-publish)
+#### [`npm publish`](/commands/npm-publish)
 
 * `prepublishOnly`
 * `prepare`
@@ -86,12 +82,12 @@ The advantage of doing these things at `prepublish` time is that they can be don
 * `publish`
 * `postpublish`
 
-#### [`npm pack`](/cli-commands/npm-pack)
+#### [`npm pack`](/commands/npm-pack)
 
 * `prepack`
 * `postpack`
 
-#### [`npm install`](/cli-commands/npm-install)
+#### [`npm install`](/commands/npm-install)
 
 * `preinstall`
 * `install`
@@ -102,7 +98,7 @@ Also triggers
 * `prepublish` (when on local)
 * `prepare` (when on local)
 
-#### [`npm start`](/cli-commands/npm-start)
+#### [`npm start`](/commands/npm-start)
 
 `npm run start` has an `npm start` shorthand.
 
@@ -304,7 +300,7 @@ above.
 
 ### See Also
 
-* [npm run-script](/cli-commands/npm-run-script)
+* [npm run-script](/commands/npm-run-script)
 * [package.json](/configuring-npm/package-json)
 * [npm developers](/using-npm/developers)
-* [npm install](/cli-commands/npm-install)
+* [npm install](/commands/npm-install)

package/node_modules/npm/docs/content/using-npm/semver.md

@@ -1,12 +1,9 @@
 ---
-section: using-npm
 title: semver
+section: 7
 description: The semantic versioner for npm
 ---
 
-semver(7) -- The semantic versioner for npm
-===========================================
-
 ## Install
 
 ```bash