A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://github.com/npm/cli/commit/dd03aa0b9acc535283daf39699de9831202348cb below:

add v9 and above for lockfile version 3 (#6921) · npm/cli@dd03aa0 · GitHub

File tree Expand file treeCollapse file tree 1 file changed

+2

-2

lines changed

Filter options

Expand file treeCollapse file tree 1 file changed

+2

-2

lines changed Original file line number Diff line number Diff line change

@@ -36,7 +36,7 @@ various purposes:

36 36

Both of these files have the same format, and perform similar functions in

37 37

the root of a project.

38 38 39 -

The difference is that `package-lock.json` cannot be published, and it will

39 +

The difference is that `package-lock.json` cannot be published, and it will

40 40

be ignored if found in any place other than the root project.

41 41 42 42

In contrast, [npm-shrinkwrap.json](/configuring-npm/npm-shrinkwrap-json) allows

@@ -114,7 +114,7 @@ the npm registry. Lockfiles generated by npm v7 will contain

114 114

* `1`: The lockfile version used by npm v5 and v6.

115 115

* `2`: The lockfile version used by npm v7 and v8. Backwards compatible to v1

116 116

lockfiles.

117 -

* `3`: The lockfile version used by npm v9. Backwards compatible to npm v7.

117 +

* `3`: The lockfile version used by npm v9 and above. Backwards compatible to npm v7.

118 118 119 119

npm will always attempt to get whatever data it can out of a lockfile, even

120 120

if it is not a version that it was designed to support.

You can’t perform that action at this time.


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4