Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Document package-lock.json v3 creation by npm v9 #450

Closed
wants to merge 1 commit into from
Closed

Document package-lock.json v3 creation by npm v9 #450

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions content/cli/v9/configuring-npm/package-lock-json.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down