Lines Matching full:package

1 .TH "PACKAGE\-LOCKS" "5" "April 2022" "" ""
3 \fBpackage-locks\fR \- An explanation of npm lockfiles
6 Conceptually, the "input" to npm help \fBinstall\fP is a npm help package\.json, while its
9 function: the same \fBpackage\.json\fP should produce the exact same \fBnode_modules\fP
14 different versions of npm (or other package managers) may have been used to install a package, each…
16 a new version of a direct semver\-range package may have been published since the last time your pa…
20 …versions (unlike the primary npm registry), and a different version of a package exists under the …
24 As an example, consider package A:
38 package B:
52 and package C:
93 …l issue, npm uses npm help package\-lock\.json or, if present, npm help npm\-shrinkwrap\.json\. Th…
95 Whenever you run \fBnpm install\fP, npm generates or updates your package lock,
123 npm help package\.json\.
125 The presence of a package lock changes the installation behavior such that:
128 The module tree described by the package lock is reproduced\. This means
130 referenced in "resolved" if available, falling back to normal package resolution
139 property of the \fBpackage\.json\fP, they will be executed in order\. \fBpreshrinkwrap\fP
141 executed afterwards\. These scripts run for both \fBpackage\-lock\.json\fP and
154 Using a locked package is no different than using any package without a package
155 lock: any commands that update \fBnode_modules\fP and/or \fBpackage\.json\fP\|'s
159 \fB\-\-no\-shrinkwrap\fP to allow \fBpackage\.json\fP to be updated while leaving
160 \fBpackage\-lock\.json\fP or \fBnpm\-shrinkwrap\.json\fP intact\.
162 It is highly recommended you commit the generated package lock to source
165 package source to get the exact same dependency tree that you were developing
171 Occasionally, two separate npm install will create package locks that cause
173 can be resolved by manually fixing any \fBpackage\.json\fP conflicts, and then
174 running \fBnpm install [\-\-package\-lock\-only]\fP again\. npm will automatically
175 resolve any conflicts for you and write a merged package lock that includes all
177 \fB\-\-package\-lock\-only\fP is provided, it will do this without also modifying your
185 \fBpackage\.json\fP itself conflicts, you will have to resolve that by hand and run
190 https://medium\.com/@sdboyer/so\-you\-want\-to\-write\-a\-package\-manager\-4ae9c17d9527
192 npm help package\.json
194 npm help package\-lock\.json