Lines Matching full:package

3 title: package-locks
7 # package-locks(5)
13 …put" to [`npm install`](/cli-commands/npm-install) is a [package.json](/configuring-npm/package-js…
16 function: the same `package.json` should produce the exact same `node_modules`
20 * different versions of npm (or other package managers) may have been used to install a package, ea…
22 * a new version of a direct semver-range package may have been published since the last time your p…
26 …versions (unlike the primary npm registry), and a different version of a package exists under the …
28 As an example, consider package A:
40 package B:
52 and package C:
86 …package-lock.json](/configuring-npm/package-lock-json) or, if present, [npm-shrinkwrap.json](/conf…
88 Whenever you run `npm install`, npm generates or updates your package lock,
114 [package.json](/configuring-npm/package-json).
116 The presence of a package lock changes the installation behavior such that:
118 1. The module tree described by the package lock is reproduced. This means
120 referenced in "resolved" if available, falling back to normal package resolution
127 property of the `package.json`, they will be executed in order. `preshrinkwrap`
129 executed afterwards. These scripts run for both `package-lock.json` and
141 Using a locked package is no different than using any package without a package
142 lock: any commands that update `node_modules` and/or `package.json`'s
146 `--no-shrinkwrap` to allow `package.json` to be updated while leaving
147 `package-lock.json` or `npm-shrinkwrap.json` intact.
149 It is highly recommended you commit the generated package lock to source
152 package source to get the exact same dependency tree that you were developing
159 Occasionally, two separate npm install will create package locks that cause
161 can be resolved by manually fixing any `package.json` conflicts, and then
162 running `npm install [--package-lock-only]` again. npm will automatically
163 resolve any conflicts for you and write a merged package lock that includes all
165 `--package-lock-only` is provided, it will do this without also modifying your
173 `package.json` itself conflicts, you will have to resolve that by hand and run
178 * https://medium.com/@sdboyer/so-you-want-to-write-a-package-manager-4ae9c17d9527
179 * [package.json](/configuring-npm/package-json)
180 * [package-lock.json](/configuring-npm/package-lock-json)