diff options
author | Kelvin Jin <kelvinjin@google.com> | 2018-11-26 19:15:21 +0300 |
---|---|---|
committer | Kat Marchán <kzm@zkat.tech> | 2018-11-26 19:15:21 +0300 |
commit | a91a470b71e08ccf6a75d4fb8c9937789fa8d067 (patch) | |
tree | f8082275f5704aa8c3dbbb4fd1bc640b1b1685ef /doc | |
parent | dcc03ec858bddd7aa2173b5a86b55c1c2385a2a3 (diff) |
docs: Specify that --dry-run isn't available in older versions of npm publish (#83)
Not sure when `--dry-run` was introduced, I assume it was introduced in npm 6 (correct me if I'm wrong). Anyway, hopefully this will prevent future developers from making the mistake of using it in npm 5 (like I did).
PR-URL: https://github.com/npm/cli/pull/83
Credit: @kjin
Reviewed-By: @zkat
Diffstat (limited to 'doc')
-rw-r--r-- | doc/cli/npm-publish.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/cli/npm-publish.md b/doc/cli/npm-publish.md index a317ff45e..c582ad847 100644 --- a/doc/cli/npm-publish.md +++ b/doc/cli/npm-publish.md @@ -47,8 +47,8 @@ specifying a different default registry or using a `npm-scope(7)` in the name don't include this and you're running from a TTY then you'll be prompted. * `[--dry-run]` - Does everything publish would do except actually publishing to the registry. - Reports the details of what would have been published. + As of `npm@6`, does everything publish would do except actually publishing + to the registry. Reports the details of what would have been published. Fails if the package name and version combination already exists in the specified registry. |