Lines Matching full:will
28 will be driven by that, with an \fBnpm\-shrinkwrap\.json\fP taking precedence if both
61 By default, \fBnpm install\fP will install all modules listed as dependencies
64 is set to \fBproduction\fP), npm will not install modules listed in
76 Its dependencies will be installed before it's linked\. If \fB<folder>\fP sits
117 In most cases, this will install the version of the modules tagged as
154 * `\-P, \-\-save\-prod`: Package will appear in your `dependencies`\. This is the
157 * `\-D, \-\-save\-dev`: Package will appear in your `devDependencies`\.
159 * `\-O, \-\-save\-optional`: Package will appear in your `optionalDependencies`\.
166 * `\-E, \-\-save\-exact`: Saved dependencies will be configured with an
170 * `\-B, \-\-save\-bundle`: Saved dependencies will also be added to your `bundleDependencies` list\.
173 will be updated as well\.
175 `<scope>` is optional\. The package will be downloaded from the registry
179 Note: if you do not include the @\-symbol on your scope name, npm will
196 working directory, then it will try to install that, and only try to
205 will fail\.
216 Install the specified version of the package\. This will fail if the
229 …will follow the same rules for resolving dependencies described in npm help \fBpackage\.json\fP\|\.
230 Note that most version ranges must be put in quotes so that your shell will
243 For a full git remote url, only that URL will be attempted\.
252 If \fB#<commit\-ish>\fP is provided, it will be used to clone exactly that
254 be any valid semver range or exact version, and npm will look for any tags
258 If the repository makes use of submodules, those submodules will be cloned
261 \fBdependencies\fP and \fBdevDependencies\fP will be installed, and the prepare
262 script will be run, before the package is packaged and installed\.
263 The following git environment variables are recognized by npm and will be
300 If \fB#<commit\-ish>\fP is provided, it will be used to clone exactly that
302 be any valid semver range or exact version, and npm will look for any tags
306 As with regular git dependencies, \fBdependencies\fP and \fBdevDependencies\fP will
321 optional and will not be saved in \fBpackage\.json\fP\|\.
322 As with regular git dependencies, \fBdependencies\fP and \fBdevDependencies\fP will
336 If \fB#<commit\-ish>\fP is provided, it will be used to clone exactly that
338 be any valid semver range or exact version, and npm will look for any tags
342 As with regular git dependencies, \fBdependencies\fP and \fBdevDependencies\fP will
356 If \fB#<commit\-ish>\fP is provided, it will be used to clone exactly that
358 be any valid semver range or exact version, and npm will look for any tags
362 As with regular git dependencies, \fBdependencies\fP and \fBdevDependencies\fP will
385 The \fB\-\-tag\fP argument will apply to all of the specified install targets\. If a
389 The \fB\-\-dry\-run\fP argument will report in the usual way what the install would
392 The \fB\-\-package\-lock\-only\fP argument will only update the \fBpackage\-lock\.json\fP,
395 The \fB\-f\fP or \fB\-\-force\fP argument will force npm to fetch remote resources even if a
404 The \fB\-\-no\-fund\fP argument will hide the message displayed at the end of each
408 The \fB\-g\fP or \fB\-\-global\fP argument will cause npm to install the package globally
411 The \fB\-\-global\-style\fP argument will cause npm to install the package into
413 global \fBnode_modules\fP folder\. Only your direct dependencies will show in
414 \fBnode_modules\fP and everything they depend on will be flattened in their
415 \fBnode_modules\fP folders\. This obviously will eliminate some deduping\.
417 The \fB\-\-ignore\-scripts\fP argument will cause npm to not execute any
420 The \fB\-\-legacy\-bundling\fP argument will cause npm to install the package such
424 The \fB\-\-link\fP argument will cause npm to link global installs into the
427 The \fB\-\-no\-bin\-links\fP argument will prevent npm from creating symlinks for
430 The \fB\-\-no\-optional\fP argument will prevent optional dependencies from
433 The \fB\-\-no\-shrinkwrap\fP argument, which will ignore an available
436 The \fB\-\-no\-package\-lock\fP argument will prevent npm from creating a
438 will not automatically prune your node modules when installing\.
440 The \fB\-\-nodedir=/path/to/node/source\fP argument will allow npm to find the
443 The \fB\-\-only={prod[uction]|dev[elopment]}\fP argument will cause either only
461 dependencies will be added as close to the top as is possible
498 Because B's D@1 will be installed in the top level, C now has to install D@2
506 npm will refuse to install any package with an identical name to the
531 affects a real use\-case, it will be investigated\.