Lines Matching full:will

15 …pm shrinkwrap file, or a yarn lock file, the installation of dependencies will be driven by that, …
56 By default, \fBnpm install\fR will install all modules listed as dependencies in \fB\fBpackage.json…
58 … the \fBNODE_ENV\fR environment variable is set to \fBproduction\fR), npm will not install modules…
67 …will be installed and may be hoisted to the top-level \fBnode_modules\fR as they would for other t…
123 In most cases, this will install the version of the modules tagged as \fBlatest\fR on the npm regis…
136 \fB-P, --save-prod\fR: Package will appear in your \fBdependencies\fR. This is the default unless \…
138 \fB-D, --save-dev\fR: Package will appear in your \fBdevDependencies\fR.
140 \fB-O, --save-optional\fR: Package will appear in your \fBoptionalDependencies\fR.
149 \fB-E, --save-exact\fR: Saved dependencies will be configured with an exact version rather than usi…
151 \fB-B, --save-bundle\fR: Saved dependencies will also be added to your \fBbundleDependencies\fR lis…
155 Further, if you have an \fBnpm-shrinkwrap.json\fR or \fBpackage-lock.json\fR then it will be update…
157 \fB<scope>\fR is optional. The package will be downloaded from the registry associated with the spe…
159 Note: if you do not include the @-symbol on your scope name, npm will interpret this as a GitHub re…
175 …le or folder named \fB<name>\fR in the current working directory, then it will try to install that…
194 …pecified tag. If the tag does not exist in the registry data for that package, then this will fail.
207 Install the specified version of the package. This will fail if the version has not been published …
220 Install a version of the package matching the specified version range. This will follow the same ru…
222 Note that most version ranges must be put in quotes so that your shell will treat it as a single ar…
235 …it provider, cloning it with \fBgit\fR. For a full git remote url, only that URL will be attempted.
245 …will be used to clone exactly that commit. If the commit-ish has the format \fB#semver:<semver>\fR…
247 If the repository makes use of submodules, those submodules will be cloned as well.
249 …pt, its \fBdependencies\fR and \fBdevDependencies\fR will be installed, and the prepare script wil…
251 The following git environment variables are recognized by npm and will be added to the environment …
291 …will be used to clone exactly that commit. If the commit-ish has the format \fB#semver:<semver>\fR…
293 As with regular git dependencies, \fBdependencies\fR and \fBdevDependencies\fR will be installed if…
306 …g \fBgit\fR. The GitHub username associated with the gist is optional and will not be saved in \fB…
308 As with regular git dependencies, \fBdependencies\fR and \fBdevDependencies\fR will be installed if…
322 …will be used to clone exactly that commit. If the commit-ish has the format \fB#semver:<semver>\fR…
324 As with regular git dependencies, \fBdependencies\fR and \fBdevDependencies\fR will be installed if…
338 …will be used to clone exactly that commit. If the commit-ish has the format \fB#semver:<semver>\fR…
340 As with regular git dependencies, \fBdependencies\fR and \fBdevDependencies\fR will be installed if…
361 The \fB--tag\fR argument will apply to all of the specified install targets. If a tag with the give…
363 The \fB--dry-run\fR argument will report in the usual way what the install would have done without …
365 The \fB--package-lock-only\fR argument will only update the \fBpackage-lock.json\fR, instead of che…
367 The \fB-f\fR or \fB--force\fR argument will force npm to fetch remote resources even if a local cop…
392 Will also prevent writing to \fBpackage-lock.json\fR if set to \fBfalse\fR.
402 Dependencies saved to package.json will be configured with an exact version rather than using npm's…
469 If a package type appears in both the \fB--include\fR and \fB--omit\fR lists, then it will be inclu…
471 If the resulting omit list includes \fB'dev'\fR, then the \fBNODE_ENV\fR environment variable will …
485 Dependency types specified in \fB--include\fR will not be omitted, regardless of the order in which…
495 …eer-deps\fR is not set, then \fIany\fR conflicting \fBpeerDependencies\fR will be treated as an in…
497 …R deep in the dependency graph will be resolved using the nearest non-peer dependency specificatio…
519 If set to false, then ignore \fBpackage-lock.json\fR files when installing. This will also prevent …
529 If set to true, the current operation will only use the \fBpackage-lock.json\fR, ignoring \fBnode_m…
531 For \fBupdate\fR this means only the \fBpackage-lock.json\fR will be updated, instead of checking \…
533 For \fBlist\fR this means the output will be based on the tree described by the \fBpackage-lock.jso…
545 Note that this will generally make installs run slower, and be much noisier, but can be useful for …
557 … test\fR, and \fBnpm run-script\fR will still run their intended script if \fBignore-scripts\fR is…
650 Path to a parent workspace directory (will result in selecting all workspaces within that folder)
668 Explicitly setting this to false will cause commands like \fBinstall\fR to ignore workspaces altoge…
671 …, update, etc.) will link workspaces into the \fBnode_modules\fR folder. - Commands that do other …
687 … \fBworkspace\fR config, or all workspaces via the \fBworkspaces\fR flag, will cause npm to operat…
699 When set file: protocol dependencies will be packed and installed as regular dependencies instead o…
727 Because B's D@1 will be installed in the top-level, C now has to install D@2 privately for itself. …