Linux worldls-302.fr.planethoster.net 4.18.0-553.8.1.lve.el7h.x86_64 #1 SMP Thu Jul 4 15:19:33 UTC 2024 x86_64
LiteSpeed
Server IP : 10.185.0.203 & Your IP : 216.73.216.32
Domains :
Cant Read [ /etc/named.conf ]
User : gerathty
Terminal
Auto Root
Create File
Create Folder
Localroot Suggester
Backdoor Destroyer
Readme
/
usr /
local /
lib /
node_modules /
npm /
doc /
files /
Delete
Unzip
Name
Size
Permission
Date
Action
npm-folders.md
7.55
KB
-rw-r--r--
2017-11-03 01:22
npm-package-locks.md
5.3
KB
-rw-r--r--
2017-11-03 01:22
npm-shrinkwrap.json.md
1.07
KB
-rw-r--r--
2017-11-03 01:22
npmrc.md
2.67
KB
-rw-r--r--
2017-11-03 01:22
package-lock.json.md
5.21
KB
-rw-r--r--
2017-11-03 01:22
package.json.md
24.64
KB
-rw-r--r--
2017-11-28 04:37
Save
Rename
npm-shrinkwrap.json(5) -- A publishable lockfile ===================================================== ## DESCRIPTION `npm-shrinkwrap.json` is a file created by npm-shrinkwrap(1). 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. Additionally, if both `package-lock.json` and `npm-shrinkwrap.json` are present in a package root, `package-lock.json` will be ignored in favor of this file. For full details and description of the `npm-shrinkwrap.json` file format, refer to the manual page for package-lock.json(5). ## SEE ALSO * npm-shrinkwrap(1) * package-lock.json(5) * package.json(5) * npm-install(1)