diff options
Diffstat (limited to 'deps/npm/doc/cli')
-rw-r--r-- | deps/npm/doc/cli/npm-access.md | 1 | ||||
-rw-r--r-- | deps/npm/doc/cli/npm-install.md | 3 | ||||
-rw-r--r-- | deps/npm/doc/cli/npm-run-script.md | 7 | ||||
-rw-r--r-- | deps/npm/doc/cli/npm-token.md | 6 |
4 files changed, 13 insertions, 4 deletions
diff --git a/deps/npm/doc/cli/npm-access.md b/deps/npm/doc/cli/npm-access.md index a338673c8d..bbccfc7093 100644 --- a/deps/npm/doc/cli/npm-access.md +++ b/deps/npm/doc/cli/npm-access.md @@ -29,7 +29,6 @@ subcommand. access to a package. * ls-packages: - Show all of the packages a user or a team is able to access, along with the access level, except for read-only public packages (it won't print the whole registry listing) diff --git a/deps/npm/doc/cli/npm-install.md b/deps/npm/doc/cli/npm-install.md index 74e5e04bca..0489ddf94e 100644 --- a/deps/npm/doc/cli/npm-install.md +++ b/deps/npm/doc/cli/npm-install.md @@ -310,6 +310,9 @@ versions. The `--dry-run` argument will report in the usual way what the install would have done without actually installing anything. +The `--package-lock-only` argument will only update the `package-lock.json`, +instead of checking `node_modules` and downloading dependencies. + The `-f` or `--force` argument will force npm to fetch remote resources even if a local copy exists on disk. diff --git a/deps/npm/doc/cli/npm-run-script.md b/deps/npm/doc/cli/npm-run-script.md index c1ce342953..ee907d8c73 100644 --- a/deps/npm/doc/cli/npm-run-script.md +++ b/deps/npm/doc/cli/npm-run-script.md @@ -44,6 +44,12 @@ instead of to run your tests. +The actual shell your script is run within is platform dependent. By default, +on Unix-like systems it is the `/bin/sh` command, on Windows it is the `cmd.exe`. +The actual shell referred to by `/bin/sh` also depends on the system. +As of [`npm@5.1.0`](https://github.com/npm/npm/releases/tag/v5.1.0) you can +customize the shell with the `script-shell` configuration. + Scripts are run from the root of the module, regardless of what your current working directory is when you call `npm run`. If you want your script to use different behavior based on what subdirectory you're in, you can use the @@ -69,3 +75,4 @@ You can use the `--silent` flag to prevent showing `npm ERR!` output on error. * npm-start(1) * npm-restart(1) * npm-stop(1) +* npm-config(7) diff --git a/deps/npm/doc/cli/npm-token.md b/deps/npm/doc/cli/npm-token.md index bc0d7596fe..82ab158af6 100644 --- a/deps/npm/doc/cli/npm-token.md +++ b/deps/npm/doc/cli/npm-token.md @@ -5,11 +5,11 @@ npm-token(1) -- Manage your authentication tokens npm token list [--json|--parseable] npm token create [--read-only] [--cidr=1.1.1.1/24,2.2.2.2/16] - npm token delete <id|token> + npm token revoke <id|token> ## DESCRIPTION -This list you list, create and delete authentication tokens. +This list you list, create and revoke authentication tokens. * `npm token list`: Shows a table of all active authentication tokens. You can request this as @@ -52,7 +52,7 @@ This list you list, create and delete authentication tokens. +----------------+--------------------------------------+ ``` -* `npm token delete <token|id>`: +* `npm token revoke <token|id>`: This removes an authentication token, making it immediately unusable. This can accept both complete tokens (as you get back from `npm token create` and will find in your `.npmrc`) and ids as seen in the `npm token list` output. |