From 2695e1fb1384ad41fe6b99fdc570088978626dd8 Mon Sep 17 00:00:00 2001
From: Tuukka Hastrup <Tuukka.Hastrup@iki.fi>
Date: Thu, 2 Mar 2023 10:23:27 +0200
Subject: [PATCH] docs: npm v9 creates package-lock.json v3 (#6187)

---
 docs/lib/content/configuring-npm/package-lock-json.md | 9 +++------
 1 file changed, 3 insertions(+), 6 deletions(-)

diff --git a/docs/lib/content/configuring-npm/package-lock-json.md b/docs/lib/content/configuring-npm/package-lock-json.md
index 4aa8dc375c89f..37dc59f3260aa 100644
--- a/docs/lib/content/configuring-npm/package-lock-json.md
+++ b/docs/lib/content/configuring-npm/package-lock-json.md
@@ -112,12 +112,9 @@ the npm registry.  Lockfiles generated by npm v7 will contain
 * No version provided: an "ancient" shrinkwrap file from a version of npm
   prior to npm v5.
 * `1`: The lockfile version used by npm v5 and v6.
-* `2`: The lockfile version used by npm v7, which is backwards compatible
-  to v1 lockfiles.
-* `3`: The lockfile version used by npm v7, _without_ backwards
-  compatibility affordances.  This is used for the hidden lockfile at
-  `node_modules/.package-lock.json`, and will likely be used in a future
-  version of npm, once support for npm v6 is no longer relevant.
+* `2`: The lockfile version used by npm v7 and v8. Backwards compatible to v1
+  lockfiles.
+* `3`: The lockfile version used by npm v9. Backwards compatible to npm v7.
 
 npm will always attempt to get whatever data it can out of a lockfile, even
 if it is not a version that it was designed to support.