Skip to content

Commit 2751b41

Browse files
lukekarryslukekarrys
committed
remove autogenerated docs content
1 parent 6319df2 commit 2751b41

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

69 files changed

+128
-9017
lines changed

‎docs/lib/content/commands/npm-access.md‎

Lines changed: 2 additions & 61 deletions
Original file line numberDiff line numberDiff line change
@@ -6,24 +6,7 @@ description: Set access level on published packages
66

77
### Synopsis
88

9-
<!-- AUTOGENERATED USAGE DESCRIPTIONS START -->
10-
<!-- automatically generated, do not edit manually -->
11-
<!-- see lib/commands/access.js -->
12-
13-
```bash
14-
npm access list packages [<user>|<scope>|<scope:team> [<package>]
15-
npm access list collaborators [<package> [<user>]]
16-
npm access get status [<package>]
17-
npm access set status=public|private [<package>]
18-
npm access set mfa=none|publish|automation [<package>]
19-
npm access grant <read-only|read-write> <scope:team> [<package>]
20-
npm access revoke <scope:team> [<package>]
21-
```
22-
23-
<!-- automatically generated, do not edit manually -->
24-
<!-- see lib/commands/access.js -->
25-
26-
<!-- AUTOGENERATED USAGE DESCRIPTIONS END -->
9+
<!-- AUTOGENERATED USAGE DESCRIPTIONS -->
2710

2811
### Description
2912

@@ -86,49 +69,7 @@ Management of teams and team memberships is done with the `npm team` command.
8669

8770
### Configuration
8871

89-
<!-- AUTOGENERATED CONFIG DESCRIPTIONS START -->
90-
<!-- automatically generated, do not edit manually -->
91-
<!-- see lib/utils/config/definitions.js -->
92-
#### `json`
93-
94-
* Default: false
95-
* Type: Boolean
96-
97-
Whether or not to output JSON data, rather than the normal output.
98-
99-
* In `npm pkg set` it enables parsing set values with JSON.parse() before
100-
saving them to your `package.json`.
101-
102-
Not supported by all npm commands.
103-
104-
<!-- automatically generated, do not edit manually -->
105-
<!-- see lib/utils/config/definitions.js -->
106-
107-
#### `otp`
108-
109-
* Default: null
110-
* Type: null or String
111-
112-
This is a one-time password from a two-factor authenticator. It's needed
113-
when publishing or changing package permissions with `npm access`.
114-
115-
If not set, and a registry response fails with a challenge for a one-time
116-
password, npm will prompt on the command line for one.
117-
118-
<!-- automatically generated, do not edit manually -->
119-
<!-- see lib/utils/config/definitions.js -->
120-
121-
#### `registry`
122-
123-
* Default: "https://registry.npmjs.org/"
124-
* Type: URL
125-
126-
The base URL of the npm registry.
127-
128-
<!-- automatically generated, do not edit manually -->
129-
<!-- see lib/utils/config/definitions.js -->
130-
131-
<!-- AUTOGENERATED CONFIG DESCRIPTIONS END -->
72+
<!-- AUTOGENERATED CONFIG DESCRIPTIONS -->
13273

13374
### See Also
13475

‎docs/lib/content/commands/npm-adduser.md‎

Lines changed: 2 additions & 71 deletions
Original file line numberDiff line numberDiff line change
@@ -6,20 +6,7 @@ description: Add a registry user account
66

77
### Synopsis
88

9-
<!-- AUTOGENERATED USAGE DESCRIPTIONS START -->
10-
<!-- automatically generated, do not edit manually -->
11-
<!-- see lib/commands/adduser.js -->
12-
13-
```bash
14-
npm adduser
15-
16-
alias: add-user
17-
```
18-
19-
<!-- automatically generated, do not edit manually -->
20-
<!-- see lib/commands/adduser.js -->
21-
22-
<!-- AUTOGENERATED USAGE DESCRIPTIONS END -->
9+
<!-- AUTOGENERATED USAGE DESCRIPTIONS -->
2310

2411
Note: This command is unaware of workspaces.
2512

@@ -34,63 +21,7 @@ email are read in from prompts.
3421

3522
### Configuration
3623

37-
<!-- AUTOGENERATED CONFIG DESCRIPTIONS START -->
38-
<!-- automatically generated, do not edit manually -->
39-
<!-- see lib/utils/config/definitions.js -->
40-
#### `registry`
41-
42-
* Default: "https://registry.npmjs.org/"
43-
* Type: URL
44-
45-
The base URL of the npm registry.
46-
47-
<!-- automatically generated, do not edit manually -->
48-
<!-- see lib/utils/config/definitions.js -->
49-
50-
#### `scope`
51-
52-
* Default: the scope of the current project, if any, or ""
53-
* Type: String
54-
55-
Associate an operation with a scope for a scoped registry.
56-
57-
Useful when logging in to or out of a private registry:
58-
59-
```
60-
# log in, linking the scope to the custom registry
61-
npm login --scope=@mycorp --registry=https://registry.mycorp.com
62-
63-
# log out, removing the link and the auth token
64-
npm logout --scope=@mycorp
65-
```
66-
67-
This will cause `@mycorp` to be mapped to the registry for future
68-
installation of packages specified according to the pattern
69-
`@mycorp/package`.
70-
71-
This will also cause `npm init` to create a scoped package.
72-
73-
```
74-
# accept all defaults, and create a package named "@foo/whatever",
75-
# instead of just named "whatever"
76-
npm init --scope=@foo --yes
77-
```
78-
79-
80-
<!-- automatically generated, do not edit manually -->
81-
<!-- see lib/utils/config/definitions.js -->
82-
83-
#### `auth-type`
84-
85-
* Default: "web"
86-
* Type: "legacy" or "web"
87-
88-
What authentication strategy to use with `login`.
89-
90-
<!-- automatically generated, do not edit manually -->
91-
<!-- see lib/utils/config/definitions.js -->
92-
93-
<!-- AUTOGENERATED CONFIG DESCRIPTIONS END -->
24+
<!-- AUTOGENERATED CONFIG DESCRIPTIONS -->
9425

9526
### See Also
9627

0 commit comments

Comments
 (0)