diff options
Diffstat (limited to 'deps/npm/man/man1/npm-dedupe.1')
| -rw-r--r-- | deps/npm/man/man1/npm-dedupe.1 | 63 |
1 files changed, 18 insertions, 45 deletions
diff --git a/deps/npm/man/man1/npm-dedupe.1 b/deps/npm/man/man1/npm-dedupe.1 index 8d2d5082a1..7db8b734db 100644 --- a/deps/npm/man/man1/npm-dedupe.1 +++ b/deps/npm/man/man1/npm-dedupe.1 @@ -6,9 +6,8 @@ .RS 2 .nf npm dedupe -npm ddp -aliases: ddp +alias: ddp .fi .RE .SS Description @@ -82,9 +81,6 @@ values in \fBpackage\.json\fP you can run: \fBnpm dedupe \-\-save\fP (or add the \fBsave=true\fP option to a npm help configuration file to make that the default behavior)\. .SS Configuration -<!\-\- AUTOGENERATED CONFIG DESCRIPTIONS START \-\-> -<!\-\- automatically generated, do not edit manually \-\-> -<!\-\- see lib/utils/config/definitions\.js \-\-> .SS \fBglobal\-style\fP .RS 0 .IP \(bu 2 @@ -100,9 +96,6 @@ direct dependencies will show in \fBnode_modules\fP and everything they depend on will be flattened in their \fBnode_modules\fP folders\. This obviously will eliminate some deduping\. If used with \fBlegacy\-bundling\fP, \fBlegacy\-bundling\fP will be preferred\. -<!\-\- automatically generated, do not edit manually \-\-> -<!\-\- see lib/utils/config/definitions\.js \-\-> - .SS \fBlegacy\-bundling\fP .RS 0 .IP \(bu 2 @@ -116,9 +109,6 @@ Causes npm to install the package such that versions of npm prior to 1\.4, such as the one included with node 0\.8, can install the package\. This eliminates all automatic deduping\. If used with \fBglobal\-style\fP this option will be preferred\. -<!\-\- automatically generated, do not edit manually \-\-> -<!\-\- see lib/utils/config/definitions\.js \-\-> - .SS \fBstrict\-peer\-deps\fP .RS 0 .IP \(bu 2 @@ -141,9 +131,6 @@ the range set in their package's \fBpeerDependencies\fP object\. When such and override is performed, a warning is printed, explaining the conflict and the packages involved\. If \fB\-\-strict\-peer\-deps\fP is set, then this warning is treated as a failure\. -<!\-\- automatically generated, do not edit manually \-\-> -<!\-\- see lib/utils/config/definitions\.js \-\-> - .SS \fBpackage\-lock\fP .RS 0 .IP \(bu 2 @@ -159,9 +146,24 @@ will also prevent \fIwriting\fR \fBpackage\-lock\.json\fP if \fBsave\fP is true\ When package package\-locks are disabled, automatic pruning of extraneous modules will also be disabled\. To remove extraneous modules with package\-locks disabled use \fBnpm prune\fP\|\. -<!\-\- automatically generated, do not edit manually \-\-> -<!\-\- see lib/utils/config/definitions\.js \-\-> +.P +This configuration does not affect \fBnpm ci\fP\|\. +.SS \fBsave\fP +.RS 0 +.IP \(bu 2 +Default: \fBtrue\fP unless when using \fBnpm update\fP or \fBnpm dedupe\fP where it +defaults to \fBfalse\fP +.IP \(bu 2 +Type: Boolean +.RE +.P +Save installed packages to a \fBpackage\.json\fP file as dependencies\. +.P +When used with the \fBnpm rm\fP command, removes the dependency from +\fBpackage\.json\fP\|\. +.P +Will also prevent writing to \fBpackage\-lock\.json\fP if set to \fBfalse\fP\|\. .SS \fBomit\fP .RS 0 .IP \(bu 2 @@ -183,9 +185,6 @@ it will be included\. .P If the resulting omit list includes \fB\|'dev'\fP, then the \fBNODE_ENV\fP environment variable will be set to \fB\|'production'\fP for all lifecycle scripts\. -<!\-\- automatically generated, do not edit manually \-\-> -<!\-\- see lib/utils/config/definitions\.js \-\-> - .SS \fBignore\-scripts\fP .RS 0 .IP \(bu 2 @@ -201,9 +200,6 @@ Note that commands explicitly intended to run a particular script, such as \fBnpm start\fP, \fBnpm stop\fP, \fBnpm restart\fP, \fBnpm test\fP, and \fBnpm run\-script\fP will still run their intended script if \fBignore\-scripts\fP is set, but they will \fInot\fR run any pre\- or post\-scripts\. -<!\-\- automatically generated, do not edit manually \-\-> -<!\-\- see lib/utils/config/definitions\.js \-\-> - .SS \fBaudit\fP .RS 0 .IP \(bu 2 @@ -217,9 +213,6 @@ When "true" submit audit reports alongside the current npm command to the default registry and all registries configured for scopes\. See the documentation for npm help \fBaudit\fP for details on what is submitted\. -<!\-\- automatically generated, do not edit manually \-\-> -<!\-\- see lib/utils/config/definitions\.js \-\-> - .SS \fBbin\-links\fP .RS 0 .IP \(bu 2 @@ -235,9 +228,6 @@ executables\. Set to false to have it not do this\. This can be used to work around the fact that some file systems don't support symlinks, even on ostensibly Unix systems\. -<!\-\- automatically generated, do not edit manually \-\-> -<!\-\- see lib/utils/config/definitions\.js \-\-> - .SS \fBfund\fP .RS 0 .IP \(bu 2 @@ -250,9 +240,6 @@ Type: Boolean When "true" displays the message at the end of each \fBnpm install\fP acknowledging the number of dependencies looking for funding\. See npm help \fBnpm fund\fP for details\. -<!\-\- automatically generated, do not edit manually \-\-> -<!\-\- see lib/utils/config/definitions\.js \-\-> - .SS \fBdry\-run\fP .RS 0 .IP \(bu 2 @@ -269,9 +256,6 @@ commands that modify your local installation, eg, \fBinstall\fP, \fBupdate\fP, .P Note: This is NOT honored by other network related commands, eg \fBdist\-tags\fP, \fBowner\fP, etc\. -<!\-\- automatically generated, do not edit manually \-\-> -<!\-\- see lib/utils/config/definitions\.js \-\-> - .SS \fBworkspace\fP .RS 0 .IP \(bu 2 @@ -302,9 +286,6 @@ workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project\. .P This value is not exported to the environment for child processes\. -<!\-\- automatically generated, do not edit manually \-\-> -<!\-\- see lib/utils/config/definitions\.js \-\-> - .SS \fBworkspaces\fP .RS 0 .IP \(bu 2 @@ -329,9 +310,6 @@ other things (test, exec, publish, etc\.) will operate on the root project, .RE .P This value is not exported to the environment for child processes\. -<!\-\- automatically generated, do not edit manually \-\-> -<!\-\- see lib/utils/config/definitions\.js \-\-> - .SS \fBinclude\-workspace\-root\fP .RS 0 .IP \(bu 2 @@ -346,11 +324,6 @@ Include the workspace root when workspaces are enabled for a command\. When false, specifying individual workspaces via the \fBworkspace\fP config, or all workspaces via the \fBworkspaces\fP flag, will cause npm to operate only on the specified workspaces, and not on the root project\. -<!\-\- automatically generated, do not edit manually \-\-> -<!\-\- see lib/utils/config/definitions\.js \-\-> - -<!\-\- AUTOGENERATED CONFIG DESCRIPTIONS END \-\-> - .SS See Also .RS 0 .IP \(bu 2 |