You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+21-3Lines changed: 21 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -20,11 +20,26 @@ Publish the package on the `npm` registry.
20
20
21
21
## Configuration
22
22
23
-
For each plugin, the `npm` authentication token has to be configured with the environment variable `NPM_TOKEN`.
23
+
### Environment variables
24
24
25
-
All the plugins are based on `npm`and will use the configuration from `.npmrc`. Any parameter returned by `npm config list` will be used by each plugin.
25
+
The `npm`authentication configuration is **required** and can be set via environment variables.
26
26
27
-
The registry and dist-tag can be configured in the `package.json` and will take precedence on the configuration in `.npmrc`:
27
+
Both the [token](https://docs.npmjs.com/getting-started/working_with_tokens) and the legacy (`username`, `password` and `email`) authentication are supported. It is recommended to use the [token](https://docs.npmjs.com/getting-started/working_with_tokens) authentication. The legacy authentication is supported as the alternative npm registries [Artifactory](https://www.jfrog.com/open-source/#os-arti) and [npm-registry-couchapp](https://github.com/npm/npm-registry-couchapp) only supports that form of authentication at this point.
|`NPM_TOKEN`| Npm token created via [npm token create](https://docs.npmjs.com/getting-started/working_with_tokens#how-to-create-new-tokens)|
32
+
|`NPM_USERNAME`| Npm username created via [npm adduser](https://docs.npmjs.com/cli/adduser) or on [npmjs.com](https://www.npmjs.com)|
33
+
|`NPM_PASSWORD`| Password of the npm user. |
34
+
|`NPM_EMAIL`| Email address associated with the npm user |
35
+
36
+
Use either `NPM_TOKEN` for token authentication or `NPM_USERNAME`, `NPM_PASSWORD` and `NPM_EMAIL` for legacy authentication
37
+
38
+
### Options
39
+
40
+
The plugins are based on `npm` and will use the configuration from [`.npmrc`](https://docs.npmjs.com/files/npmrc). See [npm config](https://docs.npmjs.com/misc/config) for the option list.
41
+
42
+
The [`registry`](https://docs.npmjs.com/misc/registry) and [`dist-tag`](https://docs.npmjs.com/cli/dist-tag) can be configured in the `package.json` and will take precedence over the configuration in `.npmrc`:
28
43
```json
29
44
{
30
45
"publishConfig": {
@@ -33,6 +48,9 @@ The registry and dist-tag can be configured in the `package.json` and will take
33
48
}
34
49
}
35
50
```
51
+
52
+
### Usage
53
+
36
54
The plugins are used by default by [semantic-release](https://github.com/semantic-release/semantic-release) so no specific configuration is requiered to use them.
37
55
38
56
Each individual plugin can be disabled, replaced or used with other plugins in the `package.json`:
0 commit comments