summaryrefslogtreecommitdiff
path: root/deps/npm/docs/content/configuring-npm/package-locks.md
diff options
context:
space:
mode:
Diffstat (limited to 'deps/npm/docs/content/configuring-npm/package-locks.md')
-rw-r--r--deps/npm/docs/content/configuring-npm/package-locks.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/deps/npm/docs/content/configuring-npm/package-locks.md b/deps/npm/docs/content/configuring-npm/package-locks.md
index 81d21298ae..de65e3c634 100644
--- a/deps/npm/docs/content/configuring-npm/package-locks.md
+++ b/deps/npm/docs/content/configuring-npm/package-locks.md
@@ -10,7 +10,7 @@ description: An explanation of npm lockfiles
### Description
-Conceptually, the "input" to [`npm install`](/cli-commands/install) is a [package.json](/configuring-npm/package-json), while its
+Conceptually, the "input" to [`npm install`](/cli-commands/npm-install) is a [package.json](/configuring-npm/package-json), while its
"output" is a fully-formed `node_modules` tree: a representation of the
dependencies you declared. In an ideal world, npm would work like a pure
function: the same `package.json` should produce the exact same `node_modules`
@@ -179,4 +179,4 @@ pre-`npm@5.7.0` versions of npm 5, albeit a bit more noisily. Note that if
* [package.json](/configuring-npm/package-json)
* [package-lock.json](/configuring-npm/package-lock-json)
* [shrinkwrap.json](/configuring-npm/shrinkwrap-json)
-* [npm shrinkwrap](/cli-commands/shrinkwrap)
+* [npm shrinkwrap](/cli-commands/npm-shrinkwrap)