Skip to content

Commit

Permalink
docs: add --dry-run to install and pack (#41)
Browse files Browse the repository at this point in the history
PR-URL: #41
Credit: @reconbot
Reviewed-By: @zkat
  • Loading branch information
reconbot authored and zkat committed Aug 20, 2018
1 parent 08ecde2 commit de95640
Show file tree
Hide file tree
Showing 4 changed files with 13 additions and 7 deletions.
5 changes: 4 additions & 1 deletion doc/cli/npm-pack.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ npm-pack(1) -- Create a tarball from a package

## SYNOPSIS

npm pack [[<@scope>/]<pkg>...]
npm pack [[<@scope>/]<pkg>...] [--dry-run]

## DESCRIPTION

Expand All @@ -18,6 +18,9 @@ overwritten the second time.

If no arguments are supplied, then npm packs the current package folder.

The `--dry-run` argument will do everything that pack usually does without
actually packing anything. Reports on what would have gone into the tarball.

## SEE ALSO

* npm-cache(1)
Expand Down
11 changes: 7 additions & 4 deletions doc/cli/npm-publish.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ npm-publish(1) -- Publish a package

## SYNOPSIS

npm publish [<tarball>|<folder>] [--tag <tag>] [--access <public|restricted>] [--otp otpcode]
npm publish [<tarball>|<folder>] [--tag <tag>] [--access <public|restricted>] [--otp otpcode] [--dry-run]

Publishes '.' if no argument supplied
Sets tag 'latest' if no --tag specified
Expand Down Expand Up @@ -46,6 +46,10 @@ specifying a different default registry or using a `npm-scope(7)` in the name
then you can provide a code from your authenticator with this. If you
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.

Fails if the package name and version combination already exists in
the specified registry.

Expand All @@ -57,9 +61,8 @@ As of `npm@5`, both a sha1sum and an integrity field with a sha512sum of the
tarball will be submitted to the registry during publication. Subsequent
installs will use the strongest supported algorithm to verify downloads.

For a "dry run" that does everything except actually publishing to the
registry, see `npm-pack(1)`, which figures out the files to be included and
packs them into a tarball to be uploaded to the registry.
Similar to `--dry-run` see `npm-pack(1)`, which figures out the files to be
included and packs them into a tarball to be uploaded to the registry.

## SEE ALSO

Expand Down
2 changes: 1 addition & 1 deletion lib/pack.js
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ const tar = require('tar')
const packlist = require('npm-packlist')
const ssri = require('ssri')

pack.usage = 'npm pack [[<@scope>/]<pkg>...]'
pack.usage = 'npm pack [[<@scope>/]<pkg>...] [--dry-run]'

// if it can be installed, it can be packed.
pack.completion = install.completion
Expand Down
2 changes: 1 addition & 1 deletion lib/publish.js
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ const readUserInfo = require('./utils/read-user-info.js')
const semver = require('semver')
const statAsync = BB.promisify(require('graceful-fs').stat)

publish.usage = 'npm publish [<tarball>|<folder>] [--tag <tag>] [--access <public|restricted>]' +
publish.usage = 'npm publish [<tarball>|<folder>] [--tag <tag>] [--access <public|restricted>] [--dry-run]' +
"\n\nPublishes '.' if no argument supplied" +
'\n\nSets tag `latest` if no --tag specified'

Expand Down

0 comments on commit de95640

Please sign in to comment.