summaryrefslogtreecommitdiff
path: root/deps/npm/docs/content/cli-commands/npm-update.md
diff options
context:
space:
mode:
Diffstat (limited to 'deps/npm/docs/content/cli-commands/npm-update.md')
-rw-r--r--[-rwxr-xr-x]deps/npm/docs/content/cli-commands/npm-update.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/deps/npm/docs/content/cli-commands/npm-update.md b/deps/npm/docs/content/cli-commands/npm-update.md
index 8203f98f65..f2e93b6dc3 100755..100644
--- a/deps/npm/docs/content/cli-commands/npm-update.md
+++ b/deps/npm/docs/content/cli-commands/npm-update.md
@@ -1,10 +1,10 @@
---
-section: cli-commands
+section: cli-commands
title: npm-update
description: Update a package
---
-# npm-update
+# npm-update(1)
## Update a package
@@ -35,8 +35,8 @@ As of `npm@2.6.1`, the `npm update` will only inspect top-level packages.
Prior versions of `npm` would also recursively inspect all dependencies.
To get the old behavior, use `npm --depth 9999 update`.
-As of `npm@5.0.0`, the `npm update` will change `package.json` to save the
-new version as the minimum required dependency. To get the old behavior,
+As of `npm@5.0.0`, the `npm update` will change `package.json` to save the
+new version as the minimum required dependency. To get the old behavior,
use `npm update --no-save`.
### Example