Linux v69820.1blu.de 4.15.0 #1 SMP Mon Sep 30 15:36:27 MSK 2024 x86_64
Apache/2.4.58
Server IP : 195.90.215.149 & Your IP : 216.73.217.80
Domains :
Cant Read [ /etc/named.conf ]
User : www-data
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
usr /
share /
doc /
npm /
configuring-npm /
Delete
Unzip
Name
Size
Permission
Date
Action
folders.md.gz
3.15
KB
-rw-r--r--
2022-12-07 23:13
install.md
2.87
KB
-rw-r--r--
2022-12-07 23:13
npm-shrinkwrap-json.md
1.22
KB
-rw-r--r--
2022-12-07 23:13
npmrc.md
3.98
KB
-rw-r--r--
2022-12-07 23:13
package-json.md.gz
11.07
KB
-rw-r--r--
2022-12-07 23:13
package-lock-json.md.gz
3.56
KB
-rw-r--r--
2022-12-07 23:13
Save
Rename
--- title: npm-shrinkwrap.json section: 5 description: A publishable lockfile --- ### Description `npm-shrinkwrap.json` is a file created by [`npm shrinkwrap`](/commands/npm-shrinkwrap). It is identical to `package-lock.json`, with one major caveat: Unlike `package-lock.json`, `npm-shrinkwrap.json` may be included when publishing a package. The recommended use-case for `npm-shrinkwrap.json` is applications deployed through the publishing process on the registry: for example, daemons and command-line tools intended as global installs or `devDependencies`. It's strongly discouraged for library authors to publish this file, since that would prevent end users from having control over transitive dependency updates. If both `package-lock.json` and `npm-shrinkwrap.json` are present in a package root, `npm-shrinkwrap.json` will be preferred over the `package-lock.json` file. For full details and description of the `npm-shrinkwrap.json` file format, refer to the manual page for [package-lock.json](/configuring-npm/package-lock-json). ### See also * [npm shrinkwrap](/commands/npm-shrinkwrap) * [package-lock.json](/configuring-npm/package-lock-json) * [package.json](/configuring-npm/package-json) * [npm install](/commands/npm-install)