From 7819f148467c33255b85608f81d52841e7f69f58 Mon Sep 17 00:00:00 2001 From: Tuukka Hastrup Date: Sat, 18 Feb 2023 01:24:14 +0200 Subject: [PATCH] Document package-lock.json v3 creation by npm v9 --- content/cli/v9/configuring-npm/package-lock-json.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/content/cli/v9/configuring-npm/package-lock-json.md b/content/cli/v9/configuring-npm/package-lock-json.md index 0392a616d84..66a0cb26b74 100644 --- a/content/cli/v9/configuring-npm/package-lock-json.md +++ b/content/cli/v9/configuring-npm/package-lock-json.md @@ -137,11 +137,11 @@ the npm registry. Lockfiles generated by npm v7 will contain * `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. - +* `3`: The lockfile version supported by npm v7, _without_ backwards + compatibility to npm v6. This is used for the hidden lockfile at + `node_modules/.package-lock.json`. This is also used for + `package-lock.json` whenever npm v9 creates a new one. + 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.