remove autogenerated docs content

npm · Oct 5, 2022 · 2751b41 · 2751b41
1 parent 6319df2
commit 2751b41
Show file tree

Hide file tree

Showing 69 changed files with 128 additions and 9,017 deletions.
diff --git a/docs/lib/content/commands/npm-access.md b/docs/lib/content/commands/npm-access.md
@@ -6,24 +6,7 @@ description: Set access level on published packages
 
 ### Synopsis
 
-<!-- AUTOGENERATED USAGE DESCRIPTIONS START -->
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/commands/access.js -->
-
-```bash
-npm access list packages [<user>|<scope>|<scope:team> [<package>]
-npm access list collaborators [<package> [<user>]]
-npm access get status [<package>]
-npm access set status=public|private [<package>]
-npm access set mfa=none|publish|automation [<package>]
-npm access grant <read-only|read-write> <scope:team> [<package>]
-npm access revoke <scope:team> [<package>]
-```
-
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/commands/access.js -->
-
-<!-- AUTOGENERATED USAGE DESCRIPTIONS END -->
+<!-- AUTOGENERATED USAGE DESCRIPTIONS -->
 
 ### Description
 
@@ -86,49 +69,7 @@ Management of teams and team memberships is done with the `npm team` command.
 
 ### Configuration
 
-<!-- AUTOGENERATED CONFIG DESCRIPTIONS START -->
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-#### `json`
-
-* Default: false
-* Type: Boolean
-
-Whether or not to output JSON data, rather than the normal output.
-
-* In `npm pkg set` it enables parsing set values with JSON.parse() before
-  saving them to your `package.json`.
-
-Not supported by all npm commands.
-
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
-#### `otp`
-
-* Default: null
-* Type: null or String
-
-This is a one-time password from a two-factor authenticator. It's needed
-when publishing or changing package permissions with `npm access`.
-
-If not set, and a registry response fails with a challenge for a one-time
-password, npm will prompt on the command line for one.
-
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
-#### `registry`
-
-* Default: "https://registry.npmjs.org/"
-* Type: URL
-
-The base URL of the npm registry.
-
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
-<!-- AUTOGENERATED CONFIG DESCRIPTIONS END -->
+<!-- AUTOGENERATED CONFIG DESCRIPTIONS -->
 
 ### See Also
 

diff --git a/docs/lib/content/commands/npm-adduser.md b/docs/lib/content/commands/npm-adduser.md
@@ -6,20 +6,7 @@ description: Add a registry user account
 
 ### Synopsis
 
-<!-- AUTOGENERATED USAGE DESCRIPTIONS START -->
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/commands/adduser.js -->
-
-```bash
-npm adduser
-
-alias: add-user
-```
-
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/commands/adduser.js -->
-
-<!-- AUTOGENERATED USAGE DESCRIPTIONS END -->
+<!-- AUTOGENERATED USAGE DESCRIPTIONS -->
 
 Note: This command is unaware of workspaces.
 
@@ -34,63 +21,7 @@ email are read in from prompts.
 
 ### Configuration
 
-<!-- AUTOGENERATED CONFIG DESCRIPTIONS START -->
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-#### `registry`
-
-* Default: "https://registry.npmjs.org/"
-* Type: URL
-
-The base URL of the npm registry.
-
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
-#### `scope`
-
-* Default: the scope of the current project, if any, or ""
-* Type: String
-
-Associate an operation with a scope for a scoped registry.
-
-Useful when logging in to or out of a private registry:
-
-```
-# log in, linking the scope to the custom registry
-npm login --scope=@mycorp --registry=https://registry.mycorp.com
-
-# log out, removing the link and the auth token
-npm logout --scope=@mycorp
-```
-
-This will cause `@mycorp` to be mapped to the registry for future
-installation of packages specified according to the pattern
-`@mycorp/package`.
-
-This will also cause `npm init` to create a scoped package.
-
-```
-# accept all defaults, and create a package named "@foo/whatever",
-# instead of just named "whatever"
-npm init --scope=@foo --yes
-```
-
-
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
-#### `auth-type`
-
-* Default: "web"
-* Type: "legacy" or "web"
-
-What authentication strategy to use with `login`.
-
-<!-- automatically generated, do not edit manually -->
-<!-- see lib/utils/config/definitions.js -->
-
-<!-- AUTOGENERATED CONFIG DESCRIPTIONS END -->
+<!-- AUTOGENERATED CONFIG DESCRIPTIONS -->
 
 ### See Also