summaryrefslogtreecommitdiff
path: root/deps/npm/docs/content/configuring-npm/package-lock-json.md
diff options
context:
space:
mode:
Diffstat (limited to 'deps/npm/docs/content/configuring-npm/package-lock-json.md')
-rw-r--r--[-rwxr-xr-x]deps/npm/docs/content/configuring-npm/package-lock-json.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/deps/npm/docs/content/configuring-npm/package-lock-json.md b/deps/npm/docs/content/configuring-npm/package-lock-json.md
index 33a74f55fe..9f3ca4683d 100755..100644
--- a/deps/npm/docs/content/configuring-npm/package-lock-json.md
+++ b/deps/npm/docs/content/configuring-npm/package-lock-json.md
@@ -4,7 +4,7 @@ title: package-lock.json
description: A manifestation of the manifest
---
-# package-lock.json
+# package-lock.json(5)
## A manifestation of the manifest
@@ -28,7 +28,7 @@ various purposes:
One key detail about `package-lock.json` is that it cannot be published, and it
will be ignored if found in any place other than the toplevel package. It shares
-a format with [npm-shrinkwrap.json](docs/configuring-npm/shrinkwrap-json), which is essentially the same file, but
+a format with [npm-shrinkwrap.json](/configuring-npm/shrinkwrap-json), which is essentially the same file, but
allows publication. This is not recommended unless deploying a CLI tool or
otherwise using the publication process for producing production packages.