diff options
Diffstat (limited to 'deps/npm/docs')
137 files changed, 20 insertions, 4128 deletions
diff --git a/deps/npm/docs/content/commands/npm-access.md b/deps/npm/docs/content/commands/npm-access.md index f7a98af6547..e707eb6f5e2 100644 --- a/deps/npm/docs/content/commands/npm-access.md +++ b/deps/npm/docs/content/commands/npm-access.md @@ -6,10 +6,6 @@ description: Set access level on published packages ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/access.js --> - ```bash npm access public [<package>] npm access restricted [<package>] @@ -22,11 +18,6 @@ npm access ls-collaborators [<package> [<user>]] npm access edit [<package>] ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/access.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description Used to set access controls on private packages. @@ -88,9 +79,6 @@ Management of teams and team memberships is done with the `npm team` command. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `registry` * Default: "https://registry.npmjs.org/" @@ -98,9 +86,6 @@ Management of teams and team memberships is done with the `npm team` command. The base URL of the npm registry. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `otp` * Default: null @@ -112,11 +97,6 @@ when publishing or changing package permissions with `npm access`. If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [`libnpmaccess`](https://npm.im/libnpmaccess) diff --git a/deps/npm/docs/content/commands/npm-adduser.md b/deps/npm/docs/content/commands/npm-adduser.md index 700aecb2255..2d040c6a4a5 100644 --- a/deps/npm/docs/content/commands/npm-adduser.md +++ b/deps/npm/docs/content/commands/npm-adduser.md @@ -6,21 +6,12 @@ description: Add a registry user account ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/adduser.js --> - ```bash npm adduser aliases: login, add-user ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/adduser.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - Note: This command is unaware of workspaces. ### Description @@ -44,9 +35,6 @@ your existing record. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `registry` * Default: "https://registry.npmjs.org/" @@ -54,9 +42,6 @@ your existing record. The base URL of the npm registry. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `scope` * Default: the scope of the current project, if any, or "" @@ -87,9 +72,6 @@ npm init --scope=@foo --yes ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `auth-type` * Default: "legacy" @@ -100,11 +82,6 @@ removed in a future version. What authentication strategy to use with `login`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm registry](/using-npm/registry) diff --git a/deps/npm/docs/content/commands/npm-audit.md b/deps/npm/docs/content/commands/npm-audit.md index 48e0a3161e8..ab639550232 100644 --- a/deps/npm/docs/content/commands/npm-audit.md +++ b/deps/npm/docs/content/commands/npm-audit.md @@ -6,19 +6,10 @@ description: Run a security audit ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/audit.js --> - ```bash npm audit [fix|signatures] ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/audit.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description The audit command submits a description of the dependencies configured in @@ -247,9 +238,6 @@ $ npm audit --audit-level=moderate ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `audit-level` * Default: null @@ -258,9 +246,6 @@ $ npm audit --audit-level=moderate The minimum level of vulnerability for `npm audit` to exit with a non-zero exit code. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `dry-run` * Default: false @@ -274,9 +259,6 @@ commands that modify your local installation, eg, `install`, `update`, Note: This is NOT honored by other network related commands, eg `dist-tags`, `owner`, etc. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `force` * Default: false @@ -303,9 +285,6 @@ mistakes, unnecessary performance degradation, and malicious input. If you don't have a clear idea of what you want to do, it is strongly recommended that you do not use this option! -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `json` * Default: false @@ -318,9 +297,6 @@ Whether or not to output JSON data, rather than the normal output. Not supported by all npm commands. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `package-lock-only` * Default: false @@ -335,9 +311,6 @@ instead of checking `node_modules` and downloading dependencies. For `list` this means the output will be based on the tree described by the `package-lock.json`, rather than the contents of `node_modules`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `omit` * Default: 'dev' if the `NODE_ENV` environment variable is set to @@ -356,9 +329,6 @@ it will be included. If the resulting omit list includes `'dev'`, then the `NODE_ENV` environment variable will be set to `'production'` for all lifecycle scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `foreground-scripts` * Default: false @@ -371,9 +341,6 @@ input, output, and error with the main npm process. Note that this will generally make installs run slower, and be much noisier, but can be useful for debugging. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `ignore-scripts` * Default: false @@ -386,9 +353,6 @@ Note that commands explicitly intended to run a particular script, such as will still run their intended script if `ignore-scripts` is set, but they will *not* run any pre- or post-scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -411,9 +375,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -432,9 +393,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -448,9 +406,6 @@ the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `install-links` * Default: false @@ -460,11 +415,6 @@ When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm install](/commands/npm-install) diff --git a/deps/npm/docs/content/commands/npm-bin.md b/deps/npm/docs/content/commands/npm-bin.md index 94b72cfd5c8..16a28a8e1c3 100644 --- a/deps/npm/docs/content/commands/npm-bin.md +++ b/deps/npm/docs/content/commands/npm-bin.md @@ -6,19 +6,10 @@ description: Display npm bin folder ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/bin.js --> - ```bash npm bin ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/bin.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - Note: This command is unaware of workspaces. ### Description @@ -27,9 +18,6 @@ Print the folder where npm will install executables. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `global` * Default: false @@ -44,11 +32,6 @@ folder instead of the current working directory. See * bin files are linked to `{prefix}/bin` * man pages are linked to `{prefix}/share/man` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm prefix](/commands/npm-prefix) diff --git a/deps/npm/docs/content/commands/npm-bugs.md b/deps/npm/docs/content/commands/npm-bugs.md index 6b45f1f18ac..153355fc694 100644 --- a/deps/npm/docs/content/commands/npm-bugs.md +++ b/deps/npm/docs/content/commands/npm-bugs.md @@ -6,21 +6,12 @@ description: Report bugs for a package in a web browser ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/bugs.js --> - ```bash npm bugs [<pkgname> [<pkgname> ...]] alias: issues ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/bugs.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description This command tries to guess at the likely location of a package's bug @@ -30,9 +21,6 @@ will search for a `package.json` in the current folder and use the `name` proper ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `browser` * Default: OS X: `"open"`, Windows: `"start"`, Others: `"xdg-open"` @@ -45,9 +33,6 @@ terminal. Set to `true` to use default system URL opener. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `registry` * Default: "https://registry.npmjs.org/" @@ -55,9 +40,6 @@ Set to `true` to use default system URL opener. The base URL of the npm registry. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -80,9 +62,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -101,9 +80,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -117,11 +93,6 @@ the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm docs](/commands/npm-docs) diff --git a/deps/npm/docs/content/commands/npm-cache.md b/deps/npm/docs/content/commands/npm-cache.md index b5eddd46c05..a6ef86dd225 100644 --- a/deps/npm/docs/content/commands/npm-cache.md +++ b/deps/npm/docs/content/commands/npm-cache.md @@ -6,10 +6,6 @@ description: Manipulates packages cache ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/cache.js --> - ```bash npm cache add <package-spec> npm cache clean [<key>] @@ -17,11 +13,6 @@ npm cache ls [<name>@<version>] npm cache verify ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/cache.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - Note: This command is unaware of workspaces. ### Description @@ -79,9 +70,6 @@ verify`. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `cache` * Default: Windows: `%LocalAppData%\npm-cache`, Posix: `~/.npm` @@ -90,11 +78,6 @@ verify`. The location of npm's cache directory. See [`npm cache`](/commands/npm-cache) -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [package spec](/using-npm/package-spec) diff --git a/deps/npm/docs/content/commands/npm-ci.md b/deps/npm/docs/content/commands/npm-ci.md index 3ecd7c6efb0..474e27cdd0d 100644 --- a/deps/npm/docs/content/commands/npm-ci.md +++ b/deps/npm/docs/content/commands/npm-ci.md @@ -6,21 +6,12 @@ description: Clean install a project ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/ci.js --> - ```bash npm ci aliases: clean-install, ic, install-clean, isntall-clean ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/ci.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description This command is similar to [`npm install`](/commands/npm-install), except @@ -81,9 +72,6 @@ cache: ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `save` * Default: `true` unless when using `npm update` where it defaults to `false` @@ -96,9 +84,6 @@ When used with the `npm rm` command, removes the dependency from Will also prevent writing to `package-lock.json` if set to `false`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `save-exact` * Default: false @@ -107,9 +92,6 @@ Will also prevent writing to `package-lock.json` if set to `false`. Dependencies saved to package.json will be configured with an exact version rather than using npm's default semver range operator. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `global` * Default: false @@ -124,9 +106,6 @@ folder instead of the current working directory. See * bin files are linked to `{prefix}/bin` * man pages are linked to `{prefix}/share/man` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `global-style` * Default: false @@ -139,9 +118,6 @@ on will be flattened in their `node_modules` folders. This obviously will eliminate some deduping. If used with `legacy-bundling`, `legacy-bundling` will be preferred. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `legacy-bundling` * Default: false @@ -152,9 +128,6 @@ such as the one included with node 0.8, can install the package. This eliminates all automatic deduping. If used with `global-style` this option will be preferred. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `omit` * Default: 'dev' if the `NODE_ENV` environment variable is set to @@ -173,9 +146,6 @@ it will be included. If the resulting omit list includes `'dev'`, then the `NODE_ENV` environment variable will be set to `'production'` for all lifecycle scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `strict-peer-deps` * Default: false @@ -195,9 +165,6 @@ When such and override is performed, a warning is printed, explaining the conflict and the packages involved. If `--strict-peer-deps` is set, then this warning is treated as a failure. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `package-lock` * Default: true @@ -208,9 +175,6 @@ will also prevent _writing_ `package-lock.json` if `save` is true. This configuration does not affect `npm ci`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `foreground-scripts` * Default: false @@ -223,9 +187,6 @@ input, output, and error with the main npm process. Note that this will generally make installs run slower, and be much noisier, but can be useful for debugging. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `ignore-scripts` * Default: false @@ -238,9 +199,6 @@ Note that commands explicitly intended to run a particular script, such as will still run their intended script if `ignore-scripts` is set, but they will *not* run any pre- or post-scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `audit` * Default: true @@ -251,9 +209,6 @@ default registry and all registries configured for scopes. See the documentation for [`npm audit`](/commands/npm-audit) for details on what is submitted. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `bin-links` * Default: true @@ -266,9 +221,6 @@ 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 --> - #### `fund` * Default: true @@ -278,9 +230,6 @@ When "true" displays the message at the end of each `npm install` acknowledging the number of dependencies looking for funding. See [`npm fund`](/commands/npm-fund) for details. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `dry-run` * Default: false @@ -294,9 +243,6 @@ commands that modify your local installation, eg, `install`, `update`, Note: This is NOT honored by other network related commands, eg `dist-tags`, `owner`, etc. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -319,9 +265,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -340,9 +283,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -356,9 +296,6 @@ the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `install-links` * Default: false @@ -368,11 +305,6 @@ When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm install](/commands/npm-install) diff --git a/deps/npm/docs/content/commands/npm-completion.md b/deps/npm/docs/content/commands/npm-completion.md index d73a98f2e50..8cbc71306c8 100644 --- a/deps/npm/docs/content/commands/npm-completion.md +++ b/deps/npm/docs/content/commands/npm-completion.md @@ -6,19 +6,10 @@ description: Tab Completion for npm ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/completion.js --> - ```bash npm completion ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/completion.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - Note: This command is unaware of workspaces. ### Description diff --git a/deps/npm/docs/content/commands/npm-config.md b/deps/npm/docs/content/commands/npm-config.md index 28c6003571d..311183b9170 100644 --- a/deps/npm/docs/content/commands/npm-config.md +++ b/deps/npm/docs/content/commands/npm-config.md @@ -6,10 +6,6 @@ description: Manage the npm configuration files ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/config.js --> - ```bash npm config set <key>=<value> [<key>=<value> ...] npm config get [<key> [<key> ...]] @@ -20,11 +16,6 @@ npm config edit alias: c ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/config.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - Note: This command is unaware of workspaces. ### Description @@ -102,9 +93,6 @@ global config. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `json` * Default: false @@ -117,9 +105,6 @@ Whether or not to output JSON data, rather than the normal output. Not supported by all npm commands. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `global` * Default: false @@ -134,9 +119,6 @@ folder instead of the current working directory. See * bin files are linked to `{prefix}/bin` * man pages are linked to `{prefix}/share/man` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `editor` * Default: The EDITOR or VISUAL environment variables, or 'notepad.exe' on @@ -145,9 +127,6 @@ folder instead of the current working directory. See The command to run for `npm edit` and `npm config edit`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `location` * Default: "user" unless `--global` is passed, which will also set this value @@ -165,9 +144,6 @@ instead of the current working directory. See * bin files are linked to `{prefix}/bin` * man pages are linked to `{prefix}/share/man` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `long` * Default: false @@ -175,11 +151,6 @@ instead of the current working directory. See Show extended information in `ls`, `search`, and `help-search`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm folders](/configuring-npm/folders) diff --git a/deps/npm/docs/content/commands/npm-dedupe.md b/deps/npm/docs/content/commands/npm-dedupe.md index 570e018342f..f7fff73dc17 100644 --- a/deps/npm/docs/content/commands/npm-dedupe.md +++ b/deps/npm/docs/content/commands/npm-dedupe.md @@ -6,21 +6,12 @@ description: Reduce duplication in the package tree ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/dedupe.js --> - ```bash npm dedupe alias: ddp ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/dedupe.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description Searches the local package tree and attempts to simplify the overall @@ -86,9 +77,6 @@ values in `package.json` you can run: `npm update --save` instead. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `global-style` * Default: false @@ -101,9 +89,6 @@ on will be flattened in their `node_modules` folders. This obviously will eliminate some deduping. If used with `legacy-bundling`, `legacy-bundling` will be preferred. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `legacy-bundling` * Default: false @@ -114,9 +99,6 @@ such as the one included with node 0.8, can install the package. This eliminates all automatic deduping. If used with `global-style` this option will be preferred. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `strict-peer-deps` * Default: false @@ -136,9 +118,6 @@ When such and override is performed, a warning is printed, explaining the conflict and the packages involved. If `--strict-peer-deps` is set, then this warning is treated as a failure. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `package-lock` * Default: true @@ -149,9 +128,6 @@ will also prevent _writing_ `package-lock.json` if `save` is true. This configuration does not affect `npm ci`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `omit` * Default: 'dev' if the `NODE_ENV` environment variable is set to @@ -170,9 +146,6 @@ it will be included. If the resulting omit list includes `'dev'`, then the `NODE_ENV` environment variable will be set to `'production'` for all lifecycle scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `ignore-scripts` * Default: false @@ -185,9 +158,6 @@ Note that commands explicitly intended to run a particular script, such as will still run their intended script if `ignore-scripts` is set, but they will *not* run any pre- or post-scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `audit` * Default: true @@ -198,9 +168,6 @@ default registry and all registries configured for scopes. See the documentation for [`npm audit`](/commands/npm-audit) for details on what is submitted. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `bin-links` * Default: true @@ -213,9 +180,6 @@ 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 --> - #### `fund` * Default: true @@ -225,9 +189,6 @@ When "true" displays the message at the end of each `npm install` acknowledging the number of dependencies looking for funding. See [`npm fund`](/commands/npm-fund) for details. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `dry-run` * Default: false @@ -241,9 +202,6 @@ commands that modify your local installation, eg, `install`, `update`, Note: This is NOT honored by other network related commands, eg `dist-tags`, `owner`, etc. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -266,9 +224,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -287,9 +242,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -303,9 +255,6 @@ the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `install-links` * Default: false @@ -315,11 +264,6 @@ When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm find-dupes](/commands/npm-find-dupes) diff --git a/deps/npm/docs/content/commands/npm-deprecate.md b/deps/npm/docs/content/commands/npm-deprecate.md index 20f65140fc7..146aab88c5b 100644 --- a/deps/npm/docs/content/commands/npm-deprecate.md +++ b/deps/npm/docs/content/commands/npm-deprecate.md @@ -6,19 +6,10 @@ description: Deprecate a version of a package ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/deprecate.js --> - ```bash npm deprecate <package-spec> <message> ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/deprecate.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - Note: This command is unaware of workspaces. ### Description @@ -51,9 +42,6 @@ format an empty string. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `registry` * Default: "https://registry.npmjs.org/" @@ -61,9 +49,6 @@ format an empty string. The base URL of the npm registry. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `otp` * Default: null @@ -75,11 +60,6 @@ when publishing or changing package permissions with `npm access`. If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [package spec](/using-npm/package-spec) diff --git a/deps/npm/docs/content/commands/npm-diff.md b/deps/npm/docs/content/commands/npm-diff.md index 7dcc8af7c3b..852fcf3d066 100644 --- a/deps/npm/docs/content/commands/npm-diff.md +++ b/deps/npm/docs/content/commands/npm-diff.md @@ -6,19 +6,10 @@ description: The registry diff command ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/diff.js --> - ```bash npm diff [...<paths>] ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/diff.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description Similar to its `git diff` counterpart, this command will print diff patches @@ -158,9 +149,6 @@ located within the folder `./lib/` and changed lines of code within the ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `diff` * Default: @@ -168,9 +156,6 @@ located within the folder `./lib/` and changed lines of code within the Define arguments to compare in `npm diff`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `diff-name-only` * Default: false @@ -178,9 +163,6 @@ Define arguments to compare in `npm diff`. Prints only filenames when using `npm diff`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `diff-unified` * Default: 3 @@ -188,9 +170,6 @@ Prints only filenames when using `npm diff`. The number of lines of context to print in `npm diff`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `diff-ignore-all-space` * Default: false @@ -198,9 +177,6 @@ The number of lines of context to print in `npm diff`. Ignore whitespace when comparing lines in `npm diff`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `diff-no-prefix` * Default: false @@ -211,9 +187,6 @@ Do not show any source or destination prefix in `npm diff` output. Note: this causes `npm diff` to ignore the `--diff-src-prefix` and `--diff-dst-prefix` configs. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `diff-src-prefix` * Default: "a/" @@ -221,9 +194,6 @@ Note: this causes `npm diff` to ignore the `--diff-src-prefix` and Source prefix to be used in `npm diff` output. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `diff-dst-prefix` * Default: "b/" @@ -231,9 +201,6 @@ Source prefix to be used in `npm diff` output. Destination prefix to be used in `npm diff` output. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `diff-text` * Default: false @@ -241,9 +208,6 @@ Destination prefix to be used in `npm diff` output. Treat all files as text in `npm diff`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `global` * Default: false @@ -258,9 +222,6 @@ folder instead of the current working directory. See * bin files are linked to `{prefix}/bin` * man pages are linked to `{prefix}/share/man` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `tag` * Default: "latest" @@ -275,9 +236,6 @@ command, if no explicit tag is given. When used by the `npm diff` command, this is the tag used to fetch the tarball that will be compared with the local files by default. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -300,9 +258,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -321,9 +276,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -336,11 +288,6 @@ all workspaces via the `workspaces` flag, will cause npm to operate only on the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. - -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> ## See Also * [npm outdated](/commands/npm-outdated) diff --git a/deps/npm/docs/content/commands/npm-dist-tag.md b/deps/npm/docs/content/commands/npm-dist-tag.md index 123e67dbf3b..d22831d2ce8 100644 --- a/deps/npm/docs/content/commands/npm-dist-tag.md +++ b/deps/npm/docs/content/commands/npm-dist-tag.md @@ -6,10 +6,6 @@ description: Modify package distribution tags ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/dist-tag.js --> - ```bash npm dist-tag add <package-spec (with version)> [<tag>] npm dist-tag rm <package-spec> <tag> @@ -18,11 +14,6 @@ npm dist-tag ls [<package-spec>] alias: dist-tags ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/dist-tag.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description Add, remove, and enumerate distribution tags on a package: @@ -99,9 +90,6 @@ not begin with a number or the letter `v`. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `workspace` * Default: @@ -124,9 +112,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -145,9 +130,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -161,11 +143,6 @@ the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [package spec](/using-npm/package-spec) diff --git a/deps/npm/docs/content/commands/npm-docs.md b/deps/npm/docs/content/commands/npm-docs.md index 790d563bdb1..e4c88dc19d3 100644 --- a/deps/npm/docs/content/commands/npm-docs.md +++ b/deps/npm/docs/content/commands/npm-docs.md @@ -6,21 +6,12 @@ description: Open documentation for a package in a web browser ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/docs.js --> - ```bash npm docs [<pkgname> [<pkgname> ...]] alias: home ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/docs.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description This command tries to guess at the likely location of a package's @@ -31,9 +22,6 @@ the `name` property. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `browser` * Default: OS X: `"open"`, Windows: `"start"`, Others: `"xdg-open"` @@ -46,9 +34,6 @@ terminal. Set to `true` to use default system URL opener. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `registry` * Default: "https://registry.npmjs.org/" @@ -56,9 +41,6 @@ Set to `true` to use default system URL opener. The base URL of the npm registry. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -81,9 +63,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -102,9 +81,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -118,11 +94,6 @@ the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm view](/commands/npm-view) diff --git a/deps/npm/docs/content/commands/npm-doctor.md b/deps/npm/docs/content/commands/npm-doctor.md index 7fb63bab16e..34d925bce91 100644 --- a/deps/npm/docs/content/commands/npm-doctor.md +++ b/deps/npm/docs/content/commands/npm-doctor.md @@ -6,19 +6,10 @@ description: Check your npm environment ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/doctor.js --> - ```bash npm doctor ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/doctor.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - Note: This command is unaware of workspaces. ### Description @@ -113,9 +104,6 @@ reset the cache. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `registry` * Default: "https://registry.npmjs.org/" @@ -123,11 +111,6 @@ reset the cache. The base URL of the npm registry. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm bugs](/commands/npm-bugs) diff --git a/deps/npm/docs/content/commands/npm-edit.md b/deps/npm/docs/content/commands/npm-edit.md index 39fc49592c5..9f6750ff175 100644 --- a/deps/npm/docs/content/commands/npm-edit.md +++ b/deps/npm/docs/content/commands/npm-edit.md @@ -6,19 +6,10 @@ description: Edit an installed package ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/edit.js --> - ```bash npm edit <pkg>[/<subpkg>...] ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/edit.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - Note: This command is unaware of workspaces. ### Description @@ -36,9 +27,6 @@ changes to your locally installed copy. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `editor` * Default: The EDITOR or VISUAL environment variables, or 'notepad.exe' on @@ -47,11 +35,6 @@ changes to your locally installed copy. The command to run for `npm edit` and `npm config edit`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm folders](/configuring-npm/folders) diff --git a/deps/npm/docs/content/commands/npm-exec.md b/deps/npm/docs/content/commands/npm-exec.md index 3d8de1ea54a..b968671ed84 100644 --- a/deps/npm/docs/content/commands/npm-exec.md +++ b/deps/npm/docs/content/commands/npm-exec.md @@ -6,10 +6,6 @@ description: Run a command from a local or remote npm package ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/exec.js --> - ```bash npm exec -- <pkg>[@<version>] [args...] npm exec --package=<pkg>[@<version>] -- <cmd> [args...] @@ -19,11 +15,6 @@ npm exec --package=foo -c '<cmd> [args...]' alias: x ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/exec.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description This command allows you to run an arbitrary command from an npm package @@ -119,9 +110,6 @@ $ npm exec -- foo@latest bar --package=@npmcli/foo ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `package` * Default: @@ -129,9 +117,6 @@ $ npm exec -- foo@latest bar --package=@npmcli/foo The package or packages to install for [`npm exec`](/commands/npm-exec) -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `call` * Default: "" @@ -145,9 +130,6 @@ npm exec --package yo --package generator-node --call "yo node" ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -170,9 +152,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -191,9 +170,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -207,11 +183,6 @@ the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### Examples Run the version of `tap` in the local dependencies, with the provided diff --git a/deps/npm/docs/content/commands/npm-explain.md b/deps/npm/docs/content/commands/npm-explain.md index 5ba2fe8206b..382429ad7e9 100644 --- a/deps/npm/docs/content/commands/npm-explain.md +++ b/deps/npm/docs/content/commands/npm-explain.md @@ -6,21 +6,12 @@ description: Explain installed packages ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/explain.js --> - ```bash npm explain <package-spec> alias: why ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/explain.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description This command will print the chain of dependencies causing a given package @@ -64,9 +55,6 @@ node_modules/nyc/node_modules/find-up ``` ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `json` * Default: false @@ -79,9 +67,6 @@ Whether or not to output JSON data, rather than the normal output. Not supported by all npm commands. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -104,11 +89,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [package spec](/using-npm/package-spec) diff --git a/deps/npm/docs/content/commands/npm-explore.md b/deps/npm/docs/content/commands/npm-explore.md index 90753c7e091..cc312a0d28c 100644 --- a/deps/npm/docs/content/commands/npm-explore.md +++ b/deps/npm/docs/content/commands/npm-explore.md @@ -6,19 +6,10 @@ description: Browse an installed package ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/explore.js --> - ```bash npm explore <pkg> [ -- <command>] ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/explore.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - Note: This command is unaware of workspaces. ### Description @@ -40,9 +31,6 @@ sure to use `npm rebuild <pkg>` if you make any changes. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `shell` * Default: SHELL environment variable, or "bash" on Posix, or "cmd.exe" on @@ -51,11 +39,6 @@ sure to use `npm rebuild <pkg>` if you make any changes. The shell to run for the `npm explore` command. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm folders](/configuring-npm/folders) diff --git a/deps/npm/docs/content/commands/npm-find-dupes.md b/deps/npm/docs/content/commands/npm-find-dupes.md index 4da6c296c6b..723f04cfb11 100644 --- a/deps/npm/docs/content/commands/npm-find-dupes.md +++ b/deps/npm/docs/content/commands/npm-find-dupes.md @@ -6,19 +6,10 @@ description: Find duplication in the package tree ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/find-dupes.js --> - ```bash npm find-dupes ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/find-dupes.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description Runs `npm dedupe` in `--dry-run` mode, making npm only output the @@ -26,9 +17,6 @@ duplications, without actually changing the package tree. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `global-style` * Default: false @@ -41,9 +29,6 @@ on will be flattened in their `node_modules` folders. This obviously will eliminate some deduping. If used with `legacy-bundling`, `legacy-bundling` will be preferred. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `legacy-bundling` * Default: false @@ -54,9 +39,6 @@ such as the one included with node 0.8, can install the package. This eliminates all automatic deduping. If used with `global-style` this option will be preferred. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `strict-peer-deps` * Default: false @@ -76,9 +58,6 @@ When such and override is performed, a warning is printed, explaining the conflict and the packages involved. If `--strict-peer-deps` is set, then this warning is treated as a failure. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `package-lock` * Default: true @@ -89,9 +68,6 @@ will also prevent _writing_ `package-lock.json` if `save` is true. This configuration does not affect `npm ci`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `omit` * Default: 'dev' if the `NODE_ENV` environment variable is set to @@ -110,9 +86,6 @@ it will be included. If the resulting omit list includes `'dev'`, then the `NODE_ENV` environment variable will be set to `'production'` for all lifecycle scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `ignore-scripts` * Default: false @@ -125,9 +98,6 @@ Note that commands explicitly intended to run a particular script, such as will still run their intended script if `ignore-scripts` is set, but they will *not* run any pre- or post-scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `audit` * Default: true @@ -138,9 +108,6 @@ default registry and all registries configured for scopes. See the documentation for [`npm audit`](/commands/npm-audit) for details on what is submitted. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `bin-links` * Default: true @@ -153,9 +120,6 @@ 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 --> - #### `fund` * Default: true @@ -165,9 +129,6 @@ When "true" displays the message at the end of each `npm install` acknowledging the number of dependencies looking for funding. See [`npm fund`](/commands/npm-fund) for details. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -190,9 +151,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -211,9 +169,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -227,9 +182,6 @@ the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `install-links` * Default: false @@ -239,11 +191,6 @@ When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm dedupe](/commands/npm-dedupe) diff --git a/deps/npm/docs/content/commands/npm-fund.md b/deps/npm/docs/content/commands/npm-fund.md index 8db0ce910de..25a6735ec75 100644 --- a/deps/npm/docs/content/commands/npm-fund.md +++ b/deps/npm/docs/content/commands/npm-fund.md @@ -6,19 +6,10 @@ description: Retrieve funding information ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/fund.js --> - ```bash npm fund [<package-spec>] ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/fund.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description This command retrieves information on how to fund the dependencies of a @@ -72,9 +63,6 @@ test-workspaces-fund@1.0.0 ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `json` * Default: false @@ -87,9 +75,6 @@ Whether or not to output JSON data, rather than the normal output. Not supported by all npm commands. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `browser` * Default: OS X: `"open"`, Windows: `"start"`, Others: `"xdg-open"` @@ -102,9 +87,6 @@ terminal. Set to `true` to use default system URL opener. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `unicode` * Default: false on windows, true on mac/unix systems with a unicode locale, @@ -114,9 +96,6 @@ Set to `true` to use default system URL opener. When set to true, npm uses unicode characters in the tree output. When false, it uses ascii characters instead of unicode glyphs. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -139,9 +118,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `which` * Default: null @@ -149,11 +125,6 @@ This value is not exported to the environment for child processes. If there are multiple funding sources, which 1-indexed source URL to open. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ## See Also * [package spec](/using-npm/package-spec) diff --git a/deps/npm/docs/content/commands/npm-help-search.md b/deps/npm/docs/content/commands/npm-help-search.md index 152f9f6bec1..d92ea03aefb 100644 --- a/deps/npm/docs/content/commands/npm-help-search.md +++ b/deps/npm/docs/content/commands/npm-help-search.md @@ -6,19 +6,10 @@ description: Search npm help documentation ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/help-search.js --> - ```bash npm help-search <text> ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/help-search.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - Note: This command is unaware of workspaces. ### Description @@ -34,9 +25,6 @@ directly. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `long` * Default: false @@ -44,11 +32,6 @@ directly. Show extended information in `ls`, `search`, and `help-search`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm](/commands/npm) diff --git a/deps/npm/docs/content/commands/npm-help.md b/deps/npm/docs/content/commands/npm-help.md index 83c595db696..48af6da7fa0 100644 --- a/deps/npm/docs/content/commands/npm-help.md +++ b/deps/npm/docs/content/commands/npm-help.md @@ -6,21 +6,12 @@ description: Get help on npm ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/help.js --> - ```bash npm help <term> [<terms..>] alias: hlep ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/help.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - Note: This command is unaware of workspaces. ### Description @@ -34,9 +25,6 @@ topic, so unique matches are equivalent to specifying a topic name. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `viewer` * Default: "man" on Posix, "browser" on Windows @@ -46,11 +34,6 @@ The program to use to view help content. Set to `"browser"` to view html help content in the default web browser. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm](/commands/npm) diff --git a/deps/npm/docs/content/commands/npm-hook.md b/deps/npm/docs/content/commands/npm-hook.md index 4a9805d02f9..1304512e33a 100644 --- a/deps/npm/docs/content/commands/npm-hook.md +++ b/deps/npm/docs/content/commands/npm-hook.md @@ -6,10 +6,6 @@ description: Manage registry hooks ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/hook.js --> - ```bash npm hook add <pkg> <url> <secret> [--type=<type>] npm hook ls [pkg] @@ -17,11 +13,6 @@ npm hook rm <id> npm hook update <id> <url> <secret> ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/hook.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - Note: This command is unaware of workspaces. ### Description @@ -94,9 +85,6 @@ $ npm hook rm id-deadbeef ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `registry` * Default: "https://registry.npmjs.org/" @@ -104,9 +92,6 @@ $ npm hook rm id-deadbeef The base URL of the npm registry. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `otp` * Default: null @@ -118,11 +103,6 @@ when publishing or changing package permissions with `npm access`. If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * ["Introducing Hooks" blog post](https://blog.npmjs.org/post/145260155635/introducing-hooks-get-notifications-of-npm) diff --git a/deps/npm/docs/content/commands/npm-init.md b/deps/npm/docs/content/commands/npm-init.md index f3124a7768d..cf8bb3936ac 100644 --- a/deps/npm/docs/content/commands/npm-init.md +++ b/deps/npm/docs/content/commands/npm-init.md @@ -6,10 +6,6 @@ description: Create a package.json file ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/init.js --> - ```bash npm init <package-spec> (same as `npx <package-spec>) npm init <@scope> (same as `npx <@scope>/create`) @@ -17,11 +13,6 @@ npm init <@scope> (same as `npx <@scope>/create`) aliases: create, innit ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/init.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description `npm init <initializer>` can be used to set up a new or existing npm @@ -165,9 +156,6 @@ dot to represent the current directory in that context, e.g: `react-app .`: ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `yes` * Default: null @@ -176,9 +164,6 @@ dot to represent the current directory in that context, e.g: `react-app .`: Automatically answer "yes" to any prompts that npm might print on the command line. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `force` * Default: false @@ -205,9 +190,6 @@ mistakes, unnecessary performance degradation, and malicious input. If you don't have a clear idea of what you want to do, it is strongly recommended that you do not use this option! -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `scope` * Default: the scope of the current project, if any, or "" @@ -238,9 +220,6 @@ npm init --scope=@foo --yes ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -263,9 +242,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -284,9 +260,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces-update` * Default: true @@ -295,9 +268,6 @@ This value is not exported to the environment for child processes. If set to true, the npm cli will run an update after operations that may possibly change the workspaces installed to the `node_modules` folder. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -311,11 +281,6 @@ the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [package spec](/using-npm/package-spec) diff --git a/deps/npm/docs/content/commands/npm-install-ci-test.md b/deps/npm/docs/content/commands/npm-install-ci-test.md index b886f8ab959..c6c7f2196da 100644 --- a/deps/npm/docs/content/commands/npm-install-ci-test.md +++ b/deps/npm/docs/content/commands/npm-install-ci-test.md @@ -6,30 +6,18 @@ description: Install a project with a clean slate and run tests ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/install-ci-test.js --> - ```bash npm install-ci-test alias: cit ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/install-ci-test.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description This command runs `npm ci` followed immediately by `npm test`. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `save` * Default: `true` unless when using `npm update` where it defaults to `false` @@ -42,9 +30,6 @@ When used with the `npm rm` command, removes the dependency from Will also prevent writing to `package-lock.json` if set to `false`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `save-exact` * Default: false @@ -53,9 +38,6 @@ Will also prevent writing to `package-lock.json` if set to `false`. Dependencies saved to package.json will be configured with an exact version rather than using npm's default semver range operator. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `global` * Default: false @@ -70,9 +52,6 @@ folder instead of the current working directory. See * bin files are linked to `{prefix}/bin` * man pages are linked to `{prefix}/share/man` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `global-style` * Default: false @@ -85,9 +64,6 @@ on will be flattened in their `node_modules` folders. This obviously will eliminate some deduping. If used with `legacy-bundling`, `legacy-bundling` will be preferred. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `legacy-bundling` * Default: false @@ -98,9 +74,6 @@ such as the one included with node 0.8, can install the package. This eliminates all automatic deduping. If used with `global-style` this option will be preferred. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `omit` * Default: 'dev' if the `NODE_ENV` environment variable is set to @@ -119,9 +92,6 @@ it will be included. If the resulting omit list includes `'dev'`, then the `NODE_ENV` environment variable will be set to `'production'` for all lifecycle scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `strict-peer-deps` * Default: false @@ -141,9 +111,6 @@ When such and override is performed, a warning is printed, explaining the conflict and the packages involved. If `--strict-peer-deps` is set, then this warning is treated as a failure. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `package-lock` * Default: true @@ -154,9 +121,6 @@ will also prevent _writing_ `package-lock.json` if `save` is true. This configuration does not affect `npm ci`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `foreground-scripts` * Default: false @@ -169,9 +133,6 @@ input, output, and error with the main npm process. Note that this will generally make installs run slower, and be much noisier, but can be useful for debugging. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `ignore-scripts` * Default: false @@ -184,9 +145,6 @@ Note that commands explicitly intended to run a particular script, such as will still run their intended script if `ignore-scripts` is set, but they will *not* run any pre- or post-scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `audit` * Default: true @@ -197,9 +155,6 @@ default registry and all registries configured for scopes. See the documentation for [`npm audit`](/commands/npm-audit) for details on what is submitted. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `bin-links` * Default: true @@ -212,9 +167,6 @@ 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 --> - #### `fund` * Default: true @@ -224,9 +176,6 @@ When "true" displays the message at the end of each `npm install` acknowledging the number of dependencies looking for funding. See [`npm fund`](/commands/npm-fund) for details. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `dry-run` * Default: false @@ -240,9 +189,6 @@ commands that modify your local installation, eg, `install`, `update`, Note: This is NOT honored by other network related commands, eg `dist-tags`, `owner`, etc. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -265,9 +211,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -286,9 +229,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -302,9 +242,6 @@ the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `install-links` * Default: false @@ -314,11 +251,6 @@ When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm install-test](/commands/npm-install-test) diff --git a/deps/npm/docs/content/commands/npm-install-test.md b/deps/npm/docs/content/commands/npm-install-test.md index d27686e731c..aa1ff35bc45 100644 --- a/deps/npm/docs/content/commands/npm-install-test.md +++ b/deps/npm/docs/content/commands/npm-install-test.md @@ -6,21 +6,12 @@ description: Install package(s) and run tests ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/install-test.js --> - ```bash npm install-test [<package-spec> ...] alias: it ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/install-test.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description This command runs an `npm install` followed immediately by an `npm test`. It @@ -28,9 +19,6 @@ takes exactly the same arguments as `npm install`. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `save` * Default: `true` unless when using `npm update` where it defaults to `false` @@ -43,9 +31,6 @@ When used with the `npm rm` command, removes the dependency from Will also prevent writing to `package-lock.json` if set to `false`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `save-exact` * Default: false @@ -54,9 +39,6 @@ Will also prevent writing to `package-lock.json` if set to `false`. Dependencies saved to package.json will be configured with an exact version rather than using npm's default semver range operator. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `global` * Default: false @@ -71,9 +53,6 @@ folder instead of the current working directory. See * bin files are linked to `{prefix}/bin` * man pages are linked to `{prefix}/share/man` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `global-style` * Default: false @@ -86,9 +65,6 @@ on will be flattened in their `node_modules` folders. This obviously will eliminate some deduping. If used with `legacy-bundling`, `legacy-bundling` will be preferred. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `legacy-bundling` * Default: false @@ -99,9 +75,6 @@ such as the one included with node 0.8, can install the package. This eliminates all automatic deduping. If used with `global-style` this option will be preferred. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `omit` * Default: 'dev' if the `NODE_ENV` environment variable is set to @@ -120,9 +93,6 @@ it will be included. If the resulting omit list includes `'dev'`, then the `NODE_ENV` environment variable will be set to `'production'` for all lifecycle scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `strict-peer-deps` * Default: false @@ -142,9 +112,6 @@ When such and override is performed, a warning is printed, explaining the conflict and the packages involved. If `--strict-peer-deps` is set, then this warning is treated as a failure. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `package-lock` * Default: true @@ -155,9 +122,6 @@ will also prevent _writing_ `package-lock.json` if `save` is true. This configuration does not affect `npm ci`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `foreground-scripts` * Default: false @@ -170,9 +134,6 @@ input, output, and error with the main npm process. Note that this will generally make installs run slower, and be much noisier, but can be useful for debugging. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `ignore-scripts` * Default: false @@ -185,9 +146,6 @@ Note that commands explicitly intended to run a particular script, such as will still run their intended script if `ignore-scripts` is set, but they will *not* run any pre- or post-scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `audit` * Default: true @@ -198,9 +156,6 @@ default registry and all registries configured for scopes. See the documentation for [`npm audit`](/commands/npm-audit) for details on what is submitted. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `bin-links` * Default: true @@ -213,9 +168,6 @@ 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 --> - #### `fund` * Default: true @@ -225,9 +177,6 @@ When "true" displays the message at the end of each `npm install` acknowledging the number of dependencies looking for funding. See [`npm fund`](/commands/npm-fund) for details. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `dry-run` * Default: false @@ -241,9 +190,6 @@ commands that modify your local installation, eg, `install`, `update`, Note: This is NOT honored by other network related commands, eg `dist-tags`, `owner`, etc. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -266,9 +212,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -287,9 +230,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -303,9 +243,6 @@ the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `install-links` * Default: false @@ -315,11 +252,6 @@ When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm install](/commands/npm-install) diff --git a/deps/npm/docs/content/commands/npm-install.md b/deps/npm/docs/content/commands/npm-install.md index 35e0df22777..dc935de70aa 100644 --- a/deps/npm/docs/content/commands/npm-install.md +++ b/deps/npm/docs/content/commands/npm-install.md @@ -6,21 +6,12 @@ description: Install a package ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/install.js --> - ```bash npm install [<package-spec> ...] aliases: add, i, in, ins, inst, insta, instal, isnt, isnta, isntal, isntall ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/install.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description This command installs a package and any packages that it depends on. If the @@ -418,9 +409,6 @@ does. These are some of the most common options related to installation. -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `save` * Default: `true` unless when using `npm update` where it defaults to `false` @@ -433,9 +421,6 @@ When used with the `npm rm` command, removes the dependency from Will also prevent writing to `package-lock.json` if set to `false`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `save-exact` * Default: false @@ -444,9 +429,6 @@ Will also prevent writing to `package-lock.json` if set to `false`. Dependencies saved to package.json will be configured with an exact version rather than using npm's default semver range operator. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `global` * Default: false @@ -461,9 +443,6 @@ folder instead of the current working directory. See * bin files are linked to `{prefix}/bin` * man pages are linked to `{prefix}/share/man` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `global-style` * Default: false @@ -476,9 +455,6 @@ on will be flattened in their `node_modules` folders. This obviously will eliminate some deduping. If used with `legacy-bundling`, `legacy-bundling` will be preferred. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `legacy-bundling` * Default: false @@ -489,9 +465,6 @@ such as the one included with node 0.8, can install the package. This eliminates all automatic deduping. If used with `global-style` this option will be preferred. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `omit` * Default: 'dev' if the `NODE_ENV` environment variable is set to @@ -510,9 +483,6 @@ it will be included. If the resulting omit list includes `'dev'`, then the `NODE_ENV` environment variable will be set to `'production'` for all lifecycle scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `strict-peer-deps` * Default: false @@ -532,9 +502,6 @@ When such and override is performed, a warning is printed, explaining the conflict and the packages involved. If `--strict-peer-deps` is set, then this warning is treated as a failure. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `package-lock` * Default: true @@ -545,9 +512,6 @@ will also prevent _writing_ `package-lock.json` if `save` is true. This configuration does not affect `npm ci`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `foreground-scripts` * Default: false @@ -560,9 +524,6 @@ input, output, and error with the main npm process. Note that this will generally make installs run slower, and be much noisier, but can be useful for debugging. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `ignore-scripts` * Default: false @@ -575,9 +536,6 @@ Note that commands explicitly intended to run a particular script, such as will still run their intended script if `ignore-scripts` is set, but they will *not* run any pre- or post-scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `audit` * Default: true @@ -588,9 +546,6 @@ default registry and all registries configured for scopes. See the documentation for [`npm audit`](/commands/npm-audit) for details on what is submitted. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `bin-links` * Default: true @@ -603,9 +558,6 @@ 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 --> - #### `fund` * Default: true @@ -615,9 +567,6 @@ When "true" displays the message at the end of each `npm install` acknowledging the number of dependencies looking for funding. See [`npm fund`](/commands/npm-fund) for details. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `dry-run` * Default: false @@ -631,9 +580,6 @@ commands that modify your local installation, eg, `install`, `update`, Note: This is NOT honored by other network related commands, eg `dist-tags`, `owner`, etc. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -656,9 +602,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -677,9 +620,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -693,9 +633,6 @@ the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `install-links` * Default: false @@ -705,11 +642,6 @@ When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### Algorithm Given a `package{dep}` structure: `A{B,C}, B{C}, C{D}`, diff --git a/deps/npm/docs/content/commands/npm-link.md b/deps/npm/docs/content/commands/npm-link.md index 8c1b422493b..07917bc8330 100644 --- a/deps/npm/docs/content/commands/npm-link.md +++ b/deps/npm/docs/content/commands/npm-link.md @@ -6,21 +6,12 @@ description: Symlink a package folder ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/link.js --> - ```bash npm link [<package-spec>] alias: ln ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/link.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description This is handy for installing your own stuff, so that you can work on it and @@ -119,9 +110,6 @@ workspace(s). ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `save` * Default: `true` unless when using `npm update` where it defaults to `false` @@ -134,9 +122,6 @@ When used with the `npm rm` command, removes the dependency from Will also prevent writing to `package-lock.json` if set to `false`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `save-exact` * Default: false @@ -145,9 +130,6 @@ Will also prevent writing to `package-lock.json` if set to `false`. Dependencies saved to package.json will be configured with an exact version rather than using npm's default semver range operator. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `global` * Default: false @@ -162,9 +144,6 @@ folder instead of the current working directory. See * bin files are linked to `{prefix}/bin` * man pages are linked to `{prefix}/share/man` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `global-style` * Default: false @@ -177,9 +156,6 @@ on will be flattened in their `node_modules` folders. This obviously will eliminate some deduping. If used with `legacy-bundling`, `legacy-bundling` will be preferred. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `legacy-bundling` * Default: false @@ -190,9 +166,6 @@ such as the one included with node 0.8, can install the package. This eliminates all automatic deduping. If used with `global-style` this option will be preferred. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `strict-peer-deps` * Default: false @@ -212,9 +185,6 @@ When such and override is performed, a warning is printed, explaining the conflict and the packages involved. If `--strict-peer-deps` is set, then this warning is treated as a failure. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `package-lock` * Default: true @@ -225,9 +195,6 @@ will also prevent _writing_ `package-lock.json` if `save` is true. This configuration does not affect `npm ci`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `omit` * Default: 'dev' if the `NODE_ENV` environment variable is set to @@ -246,9 +213,6 @@ it will be included. If the resulting omit list includes `'dev'`, then the `NODE_ENV` environment variable will be set to `'production'` for all lifecycle scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `ignore-scripts` * Default: false @@ -261,9 +225,6 @@ Note that commands explicitly intended to run a particular script, such as will still run their intended script if `ignore-scripts` is set, but they will *not* run any pre- or post-scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `audit` * Default: true @@ -274,9 +235,6 @@ default registry and all registries configured for scopes. See the documentation for [`npm audit`](/commands/npm-audit) for details on what is submitted. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `bin-links` * Default: true @@ -289,9 +247,6 @@ 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 --> - #### `fund` * Default: true @@ -301,9 +256,6 @@ When "true" displays the message at the end of each `npm install` acknowledging the number of dependencies looking for funding. See [`npm fund`](/commands/npm-fund) for details. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `dry-run` * Default: false @@ -317,9 +269,6 @@ commands that modify your local installation, eg, `install`, `update`, Note: This is NOT honored by other network related commands, eg `dist-tags`, `owner`, etc. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -342,9 +291,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -363,9 +309,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -379,9 +322,6 @@ the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `install-links` * Default: false @@ -391,11 +331,6 @@ When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [package spec](/using-npm/package-spec) diff --git a/deps/npm/docs/content/commands/npm-logout.md b/deps/npm/docs/content/commands/npm-logout.md index f0dd5cb856e..8ac3948f116 100644 --- a/deps/npm/docs/content/commands/npm-logout.md +++ b/deps/npm/docs/content/commands/npm-logout.md @@ -6,19 +6,10 @@ description: Log out of the registry ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/logout.js --> - ```bash npm logout ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/logout.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - Note: This command is unaware of workspaces. ### Description @@ -36,9 +27,6 @@ connected to that scope, if set. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `registry` * Default: "https://registry.npmjs.org/" @@ -46,9 +34,6 @@ connected to that scope, if set. The base URL of the npm registry. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `scope` * Default: the scope of the current project, if any, or "" @@ -79,11 +64,6 @@ npm init --scope=@foo --yes ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm adduser](/commands/npm-adduser) diff --git a/deps/npm/docs/content/commands/npm-ls.md b/deps/npm/docs/content/commands/npm-ls.md index a7936fafc72..43d4eb7d679 100644 --- a/deps/npm/docs/content/commands/npm-ls.md +++ b/deps/npm/docs/content/commands/npm-ls.md @@ -6,21 +6,12 @@ description: List installed packages ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/ls.js --> - ```bash npm ls <package-spec> alias: list ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/ls.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description This command will print to stdout all the versions of packages that are @@ -36,7 +27,7 @@ packages will *also* show the paths to the specified packages. For example, running `npm ls promzard` in npm's source tree will show: ```bash -npm@@VERSION@ /path/to/npm +npm@8.19.3 /path/to/npm └─┬ init-package-json@0.0.4 └── promzard@0.1.5 ``` @@ -82,9 +73,6 @@ least the default human-readable `npm ls` output in npm v8. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `all` * Default: false @@ -94,9 +82,6 @@ When running `npm outdated` and `npm ls`, setting `--all` will show all outdated or installed packages, rather than only those directly depended upon by the current project. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `json` * Default: false @@ -109,9 +94,6 @@ Whether or not to output JSON data, rather than the normal output. Not supported by all npm commands. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `long` * Default: false @@ -119,9 +101,6 @@ Not supported by all npm commands. Show extended information in `ls`, `search`, and `help-search`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `parseable` * Default: false @@ -130,9 +109,6 @@ Show extended information in `ls`, `search`, and `help-search`. Output parseable results from commands that write to standard output. For `npm search`, this will be tab-separated table format. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `global` * Default: false @@ -147,9 +123,6 @@ folder instead of the current working directory. See * bin files are linked to `{prefix}/bin` * man pages are linked to `{prefix}/share/man` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `depth` * Default: `Infinity` if `--all` is set, otherwise `1` @@ -160,9 +133,6 @@ The depth to go when recursing packages for `npm ls`. If not set, `npm ls` will show only the immediate dependencies of the root project. If `--all` is set, then npm will show all dependencies by default. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `omit` * Default: 'dev' if the `NODE_ENV` environment variable is set to @@ -181,9 +151,6 @@ it will be included. If the resulting omit list includes `'dev'`, then the `NODE_ENV` environment variable will be set to `'production'` for all lifecycle scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `link` * Default: false @@ -191,9 +158,6 @@ variable will be set to `'production'` for all lifecycle scripts. Used with `npm ls`, limiting output to only those packages that are linked. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `package-lock-only` * Default: false @@ -208,9 +172,6 @@ instead of checking `node_modules` and downloading dependencies. For `list` this means the output will be based on the tree described by the `package-lock.json`, rather than the contents of `node_modules`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `unicode` * Default: false on windows, true on mac/unix systems with a unicode locale, @@ -220,9 +181,6 @@ For `list` this means the output will be based on the tree described by the When set to true, npm uses unicode characters in the tree output. When false, it uses ascii characters instead of unicode glyphs. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -245,9 +203,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -266,9 +221,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -282,9 +234,6 @@ the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `install-links` * Default: false @@ -294,11 +243,6 @@ When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [package spec](/using-npm/package-spec) diff --git a/deps/npm/docs/content/commands/npm-org.md b/deps/npm/docs/content/commands/npm-org.md index 975581c860d..ca788b01fcb 100644 --- a/deps/npm/docs/content/commands/npm-org.md +++ b/deps/npm/docs/content/commands/npm-org.md @@ -6,10 +6,6 @@ description: Manage orgs ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/org.js --> - ```bash npm org set orgname username [developer | admin | owner] npm org rm orgname username @@ -18,11 +14,6 @@ npm org ls orgname [<username>] alias: ogr ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/org.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - Note: This command is unaware of workspaces. ### Example @@ -71,9 +62,6 @@ listing them, and finding specific ones and their roles. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `registry` * Default: "https://registry.npmjs.org/" @@ -81,9 +69,6 @@ listing them, and finding specific ones and their roles. The base URL of the npm registry. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `otp` * Default: null @@ -95,9 +80,6 @@ when publishing or changing package permissions with `npm access`. If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `json` * Default: false @@ -110,9 +92,6 @@ Whether or not to output JSON data, rather than the normal output. Not supported by all npm commands. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `parseable` * Default: false @@ -121,11 +100,6 @@ Not supported by all npm commands. Output parseable results from commands that write to standard output. For `npm search`, this will be tab-separated table format. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [using orgs](/using-npm/orgs) diff --git a/deps/npm/docs/content/commands/npm-outdated.md b/deps/npm/docs/content/commands/npm-outdated.md index c4e07a0cd36..0e1061ab168 100644 --- a/deps/npm/docs/content/commands/npm-outdated.md +++ b/deps/npm/docs/content/commands/npm-outdated.md @@ -6,19 +6,10 @@ description: Check for outdated packages ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/outdated.js --> - ```bash npm outdated [<package-spec> ...] ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/outdated.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description This command will check the registry to see if any (or, specific) installed @@ -95,9 +86,6 @@ A few things to note: ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `all` * Default: false @@ -107,9 +95,6 @@ When running `npm outdated` and `npm ls`, setting `--all` will show all outdated or installed packages, rather than only those directly depended upon by the current project. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `json` * Default: false @@ -122,9 +107,6 @@ Whether or not to output JSON data, rather than the normal output. Not supported by all npm commands. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `long` * Default: false @@ -132,9 +114,6 @@ Not supported by all npm commands. Show extended information in `ls`, `search`, and `help-search`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `parseable` * Default: false @@ -143,9 +122,6 @@ Show extended information in `ls`, `search`, and `help-search`. Output parseable results from commands that write to standard output. For `npm search`, this will be tab-separated table format. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `global` * Default: false @@ -160,9 +136,6 @@ folder instead of the current working directory. See * bin files are linked to `{prefix}/bin` * man pages are linked to `{prefix}/share/man` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -185,11 +158,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [package spec](/using-npm/package-spec) diff --git a/deps/npm/docs/content/commands/npm-owner.md b/deps/npm/docs/content/commands/npm-owner.md index ebc29ef6939..c5bace6b2bc 100644 --- a/deps/npm/docs/content/commands/npm-owner.md +++ b/deps/npm/docs/content/commands/npm-owner.md @@ -6,10 +6,6 @@ description: Manage package owners ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/owner.js --> - ```bash npm owner add <user> <package-spec> npm owner rm <user> <package-spec> @@ -18,11 +14,6 @@ npm owner ls <package-spec> alias: author ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/owner.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - Note: This command is unaware of workspaces. ### Description @@ -46,9 +37,6 @@ on the command line when changing ownership with `--otp`. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `registry` * Default: "https://registry.npmjs.org/" @@ -56,9 +44,6 @@ on the command line when changing ownership with `--otp`. The base URL of the npm registry. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `otp` * Default: null @@ -70,9 +55,6 @@ when publishing or changing package permissions with `npm access`. If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -95,9 +77,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -116,11 +95,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [package spec](/using-npm/package-spec) diff --git a/deps/npm/docs/content/commands/npm-pack.md b/deps/npm/docs/content/commands/npm-pack.md index 7921042eae8..a39f0554391 100644 --- a/deps/npm/docs/content/commands/npm-pack.md +++ b/deps/npm/docs/content/commands/npm-pack.md @@ -6,24 +6,12 @@ description: Create a tarball from a package ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/pack.js --> - ```bash npm pack <package-spec> ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/pack.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `dry-run` * Default: false @@ -37,9 +25,6 @@ commands that modify your local installation, eg, `install`, `update`, Note: This is NOT honored by other network related commands, eg `dist-tags`, `owner`, etc. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `json` * Default: false @@ -52,9 +37,6 @@ Whether or not to output JSON data, rather than the normal output. Not supported by all npm commands. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `pack-destination` * Default: "." @@ -62,9 +44,6 @@ Not supported by all npm commands. Directory in which `npm pack` will save tarballs. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -87,9 +66,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -108,9 +84,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -124,11 +97,6 @@ the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### Description For anything that's installable (that is, a package folder, tarball, diff --git a/deps/npm/docs/content/commands/npm-ping.md b/deps/npm/docs/content/commands/npm-ping.md index 161d7292f8c..812be9f002d 100644 --- a/deps/npm/docs/content/commands/npm-ping.md +++ b/deps/npm/docs/content/commands/npm-ping.md @@ -6,19 +6,10 @@ description: Ping npm registry ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/ping.js --> - ```bash npm ping ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/ping.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - Note: This command is unaware of workspaces. ### Description @@ -39,9 +30,6 @@ npm ERR! 404 Not Found - GET http://www.foo.com/-/ping?write=true ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `registry` * Default: "https://registry.npmjs.org/" @@ -49,11 +37,6 @@ npm ERR! 404 Not Found - GET http://www.foo.com/-/ping?write=true The base URL of the npm registry. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm doctor](/commands/npm-doctor) diff --git a/deps/npm/docs/content/commands/npm-pkg.md b/deps/npm/docs/content/commands/npm-pkg.md index deff7e82c69..519104457df 100644 --- a/deps/npm/docs/content/commands/npm-pkg.md +++ b/deps/npm/docs/content/commands/npm-pkg.md @@ -6,10 +6,6 @@ description: Manages your package.json ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/pkg.js --> - ```bash npm pkg set <key>=<value> [<key>=<value> ...] npm pkg get [<key> [<key> ...]] @@ -18,11 +14,6 @@ npm pkg set [<array>[<index>].<key>=<value> ...] npm pkg set [<array>[].<key>=<value> ...] ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/pkg.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description A command that automates the management of `package.json` files. @@ -183,9 +174,6 @@ npm pkg get name version --ws ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `force` * Default: false @@ -212,9 +200,6 @@ mistakes, unnecessary performance degradation, and malicious input. If you don't have a clear idea of what you want to do, it is strongly recommended that you do not use this option! -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `json` * Default: false @@ -227,9 +212,6 @@ Whether or not to output JSON data, rather than the normal output. Not supported by all npm commands. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -252,9 +234,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -272,11 +251,6 @@ other things (test, exec, publish, etc.) will operate on the root project, _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. - -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> ## See Also * [npm install](/commands/npm-install) diff --git a/deps/npm/docs/content/commands/npm-prefix.md b/deps/npm/docs/content/commands/npm-prefix.md index 39328bcc88a..2711501625d 100644 --- a/deps/npm/docs/content/commands/npm-prefix.md +++ b/deps/npm/docs/content/commands/npm-prefix.md @@ -6,19 +6,10 @@ description: Display prefix ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/prefix.js --> - ```bash npm prefix [-g] ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/prefix.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - Note: This command is unaware of workspaces. ### Description @@ -44,9 +35,6 @@ npm prefix -g ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `global` * Default: false @@ -61,11 +49,6 @@ folder instead of the current working directory. See * bin files are linked to `{prefix}/bin` * man pages are linked to `{prefix}/share/man` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm root](/commands/npm-root) diff --git a/deps/npm/docs/content/commands/npm-profile.md b/deps/npm/docs/content/commands/npm-profile.md index af1f9d8aa10..b8cdde7e151 100644 --- a/deps/npm/docs/content/commands/npm-profile.md +++ b/deps/npm/docs/content/commands/npm-profile.md @@ -6,10 +6,6 @@ description: Change settings on your registry profile ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/profile.js --> - ```bash npm profile enable-2fa [auth-only|auth-and-writes] npm profile disable-2fa @@ -17,11 +13,6 @@ npm profile get [<key>] npm profile set <key> <value> ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/profile.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - Note: This command is unaware of workspaces. ### Description @@ -83,9 +74,6 @@ Some of these commands may not be available on non npmjs.com registries. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `registry` * Default: "https://registry.npmjs.org/" @@ -93,9 +81,6 @@ Some of these commands may not be available on non npmjs.com registries. The base URL of the npm registry. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `json` * Default: false @@ -108,9 +93,6 @@ Whether or not to output JSON data, rather than the normal output. Not supported by all npm commands. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `parseable` * Default: false @@ -119,9 +101,6 @@ Not supported by all npm commands. Output parseable results from commands that write to standard output. For `npm search`, this will be tab-separated table format. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `otp` * Default: null @@ -133,11 +112,6 @@ when publishing or changing package permissions with `npm access`. If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm adduser](/commands/npm-adduser) diff --git a/deps/npm/docs/content/commands/npm-prune.md b/deps/npm/docs/content/commands/npm-prune.md index 28f02f6add1..95946d9dc96 100644 --- a/deps/npm/docs/content/commands/npm-prune.md +++ b/deps/npm/docs/content/commands/npm-prune.md @@ -6,19 +6,10 @@ description: Remove extraneous packages ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/prune.js --> - ```bash npm prune [[<@scope>/]<pkg>...] ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/prune.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description This command removes "extraneous" packages. If a package name is provided, @@ -44,9 +35,6 @@ this command can help clean up any resulting garbage. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `omit` * Default: 'dev' if the `NODE_ENV` environment variable is set to @@ -65,9 +53,6 @@ it will be included. If the resulting omit list includes `'dev'`, then the `NODE_ENV` environment variable will be set to `'production'` for all lifecycle scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `dry-run` * Default: false @@ -81,9 +66,6 @@ commands that modify your local installation, eg, `install`, `update`, Note: This is NOT honored by other network related commands, eg `dist-tags`, `owner`, etc. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `json` * Default: false @@ -96,9 +78,6 @@ Whether or not to output JSON data, rather than the normal output. Not supported by all npm commands. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `foreground-scripts` * Default: false @@ -111,9 +90,6 @@ input, output, and error with the main npm process. Note that this will generally make installs run slower, and be much noisier, but can be useful for debugging. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `ignore-scripts` * Default: false @@ -126,9 +102,6 @@ Note that commands explicitly intended to run a particular script, such as will still run their intended script if `ignore-scripts` is set, but they will *not* run any pre- or post-scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -151,9 +124,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -172,9 +142,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -188,9 +155,6 @@ the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `install-links` * Default: false @@ -200,11 +164,6 @@ When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm uninstall](/commands/npm-uninstall) diff --git a/deps/npm/docs/content/commands/npm-publish.md b/deps/npm/docs/content/commands/npm-publish.md index 536d04988e6..4963cf158a6 100644 --- a/deps/npm/docs/content/commands/npm-publish.md +++ b/deps/npm/docs/content/commands/npm-publish.md @@ -6,19 +6,10 @@ description: Publish a package ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/publish.js --> - ```bash npm publish <package-spec> ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/publish.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description Publishes a package to the registry so that it can be installed by name. @@ -96,9 +87,6 @@ built. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `tag` * Default: "latest" @@ -113,9 +101,6 @@ command, if no explicit tag is given. When used by the `npm diff` command, this is the tag used to fetch the tarball that will be compared with the local files by default. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `access` * Default: 'restricted' for scoped packages, 'public' for unscoped packages @@ -132,9 +117,6 @@ subsequent `npm publish` commands using the `--access` flag will not have an effect to the access level. To make changes to the access level after the initial publish use `npm access`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `dry-run` * Default: false @@ -148,9 +130,6 @@ commands that modify your local installation, eg, `install`, `update`, Note: This is NOT honored by other network related commands, eg `dist-tags`, `owner`, etc. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `otp` * Default: null @@ -162,9 +141,6 @@ when publishing or changing package permissions with `npm access`. If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -187,9 +163,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -208,9 +181,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -224,11 +194,6 @@ the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [package spec](/using-npm/package-spec) diff --git a/deps/npm/docs/content/commands/npm-query.md b/deps/npm/docs/content/commands/npm-query.md index 3c35e9ab427..5a6bfb79cee 100644 --- a/deps/npm/docs/content/commands/npm-query.md +++ b/deps/npm/docs/content/commands/npm-query.md @@ -6,19 +6,10 @@ description: Dependency selector query ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/query.js --> - ```bash npm query <selector> ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/query.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description The `npm query` command allows for usage of css selectors in order to retrieve @@ -147,9 +138,6 @@ npm query ":type(git)" | jq 'map(.name)' | xargs -I {} npm why {} ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `global` * Default: false @@ -164,9 +152,6 @@ folder instead of the current working directory. See * bin files are linked to `{prefix}/bin` * man pages are linked to `{prefix}/share/man` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -189,9 +174,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -210,9 +192,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -225,11 +204,6 @@ all workspaces via the `workspaces` flag, will cause npm to operate only on the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. - -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> ## See Also * [dependency selectors](/using-npm/dependency-selectors) diff --git a/deps/npm/docs/content/commands/npm-rebuild.md b/deps/npm/docs/content/commands/npm-rebuild.md index 6a396421213..75f1efe1b69 100644 --- a/deps/npm/docs/content/commands/npm-rebuild.md +++ b/deps/npm/docs/content/commands/npm-rebuild.md @@ -6,21 +6,12 @@ description: Rebuild a package ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/rebuild.js --> - ```bash npm rebuild [<package-spec>] ...] alias: rb ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/rebuild.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description This command runs the `npm build` command on the matched folders. This is @@ -34,9 +25,6 @@ name and version matching one of the specifiers will be rebuilt. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `global` * Default: false @@ -51,9 +39,6 @@ folder instead of the current working directory. See * bin files are linked to `{prefix}/bin` * man pages are linked to `{prefix}/share/man` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `bin-links` * Default: true @@ -66,9 +51,6 @@ 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 --> - #### `foreground-scripts` * Default: false @@ -81,9 +63,6 @@ input, output, and error with the main npm process. Note that this will generally make installs run slower, and be much noisier, but can be useful for debugging. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `ignore-scripts` * Default: false @@ -96,9 +75,6 @@ Note that commands explicitly intended to run a particular script, such as will still run their intended script if `ignore-scripts` is set, but they will *not* run any pre- or post-scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -121,9 +97,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -142,9 +115,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -158,9 +128,6 @@ the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `install-links` * Default: false @@ -170,11 +137,6 @@ When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [package spec](/using-npm/package-spec) diff --git a/deps/npm/docs/content/commands/npm-repo.md b/deps/npm/docs/content/commands/npm-repo.md index fc540a9382b..eb55780de90 100644 --- a/deps/npm/docs/content/commands/npm-repo.md +++ b/deps/npm/docs/content/commands/npm-repo.md @@ -6,19 +6,10 @@ description: Open package repository page in the browser ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/repo.js --> - ```bash npm repo [<pkgname> [<pkgname> ...]] ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/repo.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description This command tries to guess at the likely location of a package's @@ -28,9 +19,6 @@ in the current folder and use the `repository` property. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `browser` * Default: OS X: `"open"`, Windows: `"start"`, Others: `"xdg-open"` @@ -43,9 +31,6 @@ terminal. Set to `true` to use default system URL opener. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `registry` * Default: "https://registry.npmjs.org/" @@ -53,9 +38,6 @@ Set to `true` to use default system URL opener. The base URL of the npm registry. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -78,9 +60,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -99,9 +78,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -115,11 +91,6 @@ the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm docs](/commands/npm-docs) diff --git a/deps/npm/docs/content/commands/npm-restart.md b/deps/npm/docs/content/commands/npm-restart.md index 048bebb1659..6c31cfceb51 100644 --- a/deps/npm/docs/content/commands/npm-restart.md +++ b/deps/npm/docs/content/commands/npm-restart.md @@ -6,19 +6,10 @@ description: Restart a package ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/restart.js --> - ```bash npm restart [-- <args>] ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/restart.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description This restarts a project. It is equivalent to running `npm run-script @@ -45,9 +36,6 @@ If it does _not_ have a `"restart"` script specified, but it does have ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `ignore-scripts` * Default: false @@ -60,9 +48,6 @@ Note that commands explicitly intended to run a particular script, such as will still run their intended script if `ignore-scripts` is set, but they will *not* run any pre- or post-scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `script-shell` * Default: '/bin/sh' on POSIX systems, 'cmd.exe' on Windows @@ -71,11 +56,6 @@ will *not* run any pre- or post-scripts. The shell to use for scripts run with the `npm exec`, `npm run` and `npm init <package-spec>` commands. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm run-script](/commands/npm-run-script) diff --git a/deps/npm/docs/content/commands/npm-root.md b/deps/npm/docs/content/commands/npm-root.md index 40b58e4b33d..89195744c9d 100644 --- a/deps/npm/docs/content/commands/npm-root.md +++ b/deps/npm/docs/content/commands/npm-root.md @@ -6,19 +6,10 @@ description: Display npm root ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/root.js --> - ```bash npm root ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/root.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description Print the effective `node_modules` folder to standard out. @@ -34,9 +25,6 @@ echo "Global packages installed in: ${global_node_modules}" ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `global` * Default: false @@ -51,11 +39,6 @@ folder instead of the current working directory. See * bin files are linked to `{prefix}/bin` * man pages are linked to `{prefix}/share/man` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm prefix](/commands/npm-prefix) diff --git a/deps/npm/docs/content/commands/npm-run-script.md b/deps/npm/docs/content/commands/npm-run-script.md index f606ec6bf59..16a5c693f9b 100644 --- a/deps/npm/docs/content/commands/npm-run-script.md +++ b/deps/npm/docs/content/commands/npm-run-script.md @@ -6,21 +6,12 @@ description: Run arbitrary package scripts ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/run-script.js --> - ```bash npm run-script <command> [-- <args>] aliases: run, rum, urn ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/run-script.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description This runs an arbitrary command from a package's `"scripts"` object. If no @@ -143,9 +134,6 @@ packages. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `workspace` * Default: @@ -168,9 +156,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -189,9 +174,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -205,9 +187,6 @@ the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `if-present` * Default: false @@ -222,9 +201,6 @@ CI setup. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `ignore-scripts` * Default: false @@ -237,9 +213,6 @@ Note that commands explicitly intended to run a particular script, such as will still run their intended script if `ignore-scripts` is set, but they will *not* run any pre- or post-scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `foreground-scripts` * Default: false @@ -252,9 +225,6 @@ input, output, and error with the main npm process. Note that this will generally make installs run slower, and be much noisier, but can be useful for debugging. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `script-shell` * Default: '/bin/sh' on POSIX systems, 'cmd.exe' on Windows @@ -263,11 +233,6 @@ but can be useful for debugging. The shell to use for scripts run with the `npm exec`, `npm run` and `npm init <package-spec>` commands. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm scripts](/using-npm/scripts) diff --git a/deps/npm/docs/content/commands/npm-search.md b/deps/npm/docs/content/commands/npm-search.md index 340dea9684d..3e4fa455395 100644 --- a/deps/npm/docs/content/commands/npm-search.md +++ b/deps/npm/docs/content/commands/npm-search.md @@ -6,21 +6,12 @@ description: Search for packages ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/search.js --> - ```bash npm search [search terms ...] aliases: find, s, se ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/search.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - Note: This command is unaware of workspaces. ### Description @@ -48,9 +39,6 @@ expression characters in most shells.) ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `long` * Default: false @@ -58,9 +46,6 @@ expression characters in most shells.) Show extended information in `ls`, `search`, and `help-search`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `json` * Default: false @@ -73,9 +58,6 @@ Whether or not to output JSON data, rather than the normal output. Not supported by all npm commands. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `color` * Default: true unless the NO_COLOR environ is set to something other than '0' @@ -84,9 +66,6 @@ Not supported by all npm commands. If false, never shows colors. If `"always"` then always shows colors. If true, then only prints color codes for tty file descriptors. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `parseable` * Default: false @@ -95,9 +74,6 @@ true, then only prints color codes for tty file descriptors. Output parseable results from commands that write to standard output. For `npm search`, this will be tab-separated table format. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `description` * Default: true @@ -105,9 +81,6 @@ Output parseable results from commands that write to standard output. For Show the description in `npm search` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `searchopts` * Default: "" @@ -115,9 +88,6 @@ Show the description in `npm search` Space-separated options that are always passed to search. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `searchexclude` * Default: "" @@ -125,9 +95,6 @@ Space-separated options that are always passed to search. Space-separated options that limit the results from search. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `registry` * Default: "https://registry.npmjs.org/" @@ -135,9 +102,6 @@ Space-separated options that limit the results from search. The base URL of the npm registry. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `prefer-online` * Default: false @@ -146,9 +110,6 @@ The base URL of the npm registry. If true, staleness checks for cached data will be forced, making the CLI look for updates immediately even for fresh package data. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `prefer-offline` * Default: false @@ -158,9 +119,6 @@ If true, staleness checks for cached data will be bypassed, but missing data will be requested from the server. To force full offline mode, use `--offline`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `offline` * Default: false @@ -169,11 +127,6 @@ will be requested from the server. To force full offline mode, use Force offline mode: no network requests will be done during install. To allow the CLI to fill in missing cache data, see `--prefer-offline`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm registry](/using-npm/registry) diff --git a/deps/npm/docs/content/commands/npm-set-script.md b/deps/npm/docs/content/commands/npm-set-script.md index 8695b43f144..9bbf09ea907 100644 --- a/deps/npm/docs/content/commands/npm-set-script.md +++ b/deps/npm/docs/content/commands/npm-set-script.md @@ -9,19 +9,10 @@ An npm command that lets you create a task in the `scripts` section of the `pack Deprecated. -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/set-script.js --> - ```bash npm set-script [<script>] [<command>] ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/set-script.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - **Example:** @@ -39,9 +30,6 @@ npm set-script [<script>] [<command>] ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `workspace` * Default: @@ -64,9 +52,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -85,9 +70,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -101,11 +83,6 @@ the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm run-script](/commands/npm-run-script) diff --git a/deps/npm/docs/content/commands/npm-shrinkwrap.md b/deps/npm/docs/content/commands/npm-shrinkwrap.md index 043b4ad1b1b..6786229469d 100644 --- a/deps/npm/docs/content/commands/npm-shrinkwrap.md +++ b/deps/npm/docs/content/commands/npm-shrinkwrap.md @@ -6,19 +6,10 @@ description: Lock down dependency versions for publication ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/shrinkwrap.js --> - ```bash npm shrinkwrap ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/shrinkwrap.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - Note: This command is unaware of workspaces. ### Description diff --git a/deps/npm/docs/content/commands/npm-star.md b/deps/npm/docs/content/commands/npm-star.md index 3e81c6a55bb..ba70051f10a 100644 --- a/deps/npm/docs/content/commands/npm-star.md +++ b/deps/npm/docs/content/commands/npm-star.md @@ -6,19 +6,10 @@ description: Mark your favorite packages ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/star.js --> - ```bash npm star [<package-spec>...] ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/star.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - Note: This command is unaware of workspaces. ### Description @@ -44,9 +35,6 @@ You can see all your starred packages using [`npm stars`](/commands/npm-stars) ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `registry` * Default: "https://registry.npmjs.org/" @@ -54,9 +42,6 @@ You can see all your starred packages using [`npm stars`](/commands/npm-stars) The base URL of the npm registry. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `unicode` * Default: false on windows, true on mac/unix systems with a unicode locale, @@ -66,9 +51,6 @@ The base URL of the npm registry. When set to true, npm uses unicode characters in the tree output. When false, it uses ascii characters instead of unicode glyphs. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `otp` * Default: null @@ -80,11 +62,6 @@ when publishing or changing package permissions with `npm access`. If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [package spec](/using-npm/package-spec) diff --git a/deps/npm/docs/content/commands/npm-stars.md b/deps/npm/docs/content/commands/npm-stars.md index b9153831533..114cde202e2 100644 --- a/deps/npm/docs/content/commands/npm-stars.md +++ b/deps/npm/docs/content/commands/npm-stars.md @@ -6,19 +6,10 @@ description: View packages marked as favorites ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/stars.js --> - ```bash npm stars [<user>] ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/stars.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - Note: This command is unaware of workspaces. ### Description @@ -31,9 +22,6 @@ you will most certainly enjoy this command. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `registry` * Default: "https://registry.npmjs.org/" @@ -41,11 +29,6 @@ you will most certainly enjoy this command. The base URL of the npm registry. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm star](/commands/npm-star) diff --git a/deps/npm/docs/content/commands/npm-start.md b/deps/npm/docs/content/commands/npm-start.md index 148f92606d8..7ba8425ffa4 100644 --- a/deps/npm/docs/content/commands/npm-start.md +++ b/deps/npm/docs/content/commands/npm-start.md @@ -6,19 +6,10 @@ description: Start a package ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/start.js --> - ```bash npm start [-- <args>] ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/start.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description This runs a predefined command specified in the `"start"` property of @@ -56,9 +47,6 @@ npm start ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `ignore-scripts` * Default: false @@ -71,9 +59,6 @@ Note that commands explicitly intended to run a particular script, such as will still run their intended script if `ignore-scripts` is set, but they will *not* run any pre- or post-scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `script-shell` * Default: '/bin/sh' on POSIX systems, 'cmd.exe' on Windows @@ -82,11 +67,6 @@ will *not* run any pre- or post-scripts. The shell to use for scripts run with the `npm exec`, `npm run` and `npm init <package-spec>` commands. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm run-script](/commands/npm-run-script) diff --git a/deps/npm/docs/content/commands/npm-stop.md b/deps/npm/docs/content/commands/npm-stop.md index a3084e8432b..05df3fb7d74 100644 --- a/deps/npm/docs/content/commands/npm-stop.md +++ b/deps/npm/docs/content/commands/npm-stop.md @@ -6,19 +6,10 @@ description: Stop a package ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/stop.js --> - ```bash npm stop [-- <args>] ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/stop.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description This runs a predefined command specified in the "stop" property of a @@ -49,9 +40,6 @@ npm stop ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `ignore-scripts` * Default: false @@ -64,9 +52,6 @@ Note that commands explicitly intended to run a particular script, such as will still run their intended script if `ignore-scripts` is set, but they will *not* run any pre- or post-scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `script-shell` * Default: '/bin/sh' on POSIX systems, 'cmd.exe' on Windows @@ -75,11 +60,6 @@ will *not* run any pre- or post-scripts. The shell to use for scripts run with the `npm exec`, `npm run` and `npm init <package-spec>` commands. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm run-script](/commands/npm-run-script) diff --git a/deps/npm/docs/content/commands/npm-team.md b/deps/npm/docs/content/commands/npm-team.md index dc26fb53aaf..d4374c67c31 100644 --- a/deps/npm/docs/content/commands/npm-team.md +++ b/deps/npm/docs/content/commands/npm-team.md @@ -6,10 +6,6 @@ description: Manage organization teams and team memberships ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/team.js --> - ```bash npm team create <scope:team> [--otp <otpcode>] npm team destroy <scope:team> [--otp <otpcode>] @@ -18,11 +14,6 @@ npm team rm <scope:team> <user> [--otp <otpcode>] npm team ls <scope>|<scope:team> ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/team.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - Note: This command is unaware of workspaces. ### Description @@ -110,9 +101,6 @@ use the `npm access` command to grant or revoke the appropriate permissions. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `registry` * Default: "https://registry.npmjs.org/" @@ -120,9 +108,6 @@ use the `npm access` command to grant or revoke the appropriate permissions. The base URL of the npm registry. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `otp` * Default: null @@ -134,9 +119,6 @@ when publishing or changing package permissions with `npm access`. If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `parseable` * Default: false @@ -145,9 +127,6 @@ password, npm will prompt on the command line for one. Output parseable results from commands that write to standard output. For `npm search`, this will be tab-separated table format. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `json` * Default: false @@ -160,11 +139,6 @@ Whether or not to output JSON data, rather than the normal output. Not supported by all npm commands. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm access](/commands/npm-access) diff --git a/deps/npm/docs/content/commands/npm-test.md b/deps/npm/docs/content/commands/npm-test.md index 72bb899d0b9..ffdb578d10f 100644 --- a/deps/npm/docs/content/commands/npm-test.md +++ b/deps/npm/docs/content/commands/npm-test.md @@ -6,21 +6,12 @@ description: Test a package ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/test.js --> - ```bash npm test [-- <args>] aliases: tst, t ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/test.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description This runs a predefined command specified in the `"test"` property of @@ -46,9 +37,6 @@ npm test ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `ignore-scripts` * Default: false @@ -61,9 +49,6 @@ Note that commands explicitly intended to run a particular script, such as will still run their intended script if `ignore-scripts` is set, but they will *not* run any pre- or post-scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `script-shell` * Default: '/bin/sh' on POSIX systems, 'cmd.exe' on Windows @@ -72,11 +57,6 @@ will *not* run any pre- or post-scripts. The shell to use for scripts run with the `npm exec`, `npm run` and `npm init <package-spec>` commands. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm run-script](/commands/npm-run-script) diff --git a/deps/npm/docs/content/commands/npm-token.md b/deps/npm/docs/content/commands/npm-token.md index 856ad68c9c9..bfd8e05a14f 100644 --- a/deps/npm/docs/content/commands/npm-token.md +++ b/deps/npm/docs/content/commands/npm-token.md @@ -6,21 +6,12 @@ description: Manage your authentication tokens ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/token.js --> - ```bash npm token list npm token revoke <id|token> npm token create [--read-only] [--cidr=list] ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/token.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - Note: This command is unaware of workspaces. ### Description @@ -86,9 +77,6 @@ This lets you list, create and revoke authentication tokens. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `read-only` * Default: false @@ -97,9 +85,6 @@ This lets you list, create and revoke authentication tokens. This is used to mark a token as unable to publish when configuring limited access tokens with the `npm token create` command. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `cidr` * Default: null @@ -108,9 +93,6 @@ access tokens with the `npm token create` command. This is a list of CIDR address to be used when configuring limited access tokens with the `npm token create` command. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `registry` * Default: "https://registry.npmjs.org/" @@ -118,9 +100,6 @@ tokens with the `npm token create` command. The base URL of the npm registry. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `otp` * Default: null @@ -132,11 +111,6 @@ when publishing or changing package permissions with `npm access`. If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm adduser](/commands/npm-adduser) diff --git a/deps/npm/docs/content/commands/npm-uninstall.md b/deps/npm/docs/content/commands/npm-uninstall.md index e39c7e328b2..25bfb4e4c21 100644 --- a/deps/npm/docs/content/commands/npm-uninstall.md +++ b/deps/npm/docs/content/commands/npm-uninstall.md @@ -6,21 +6,12 @@ description: Remove a package ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/uninstall.js --> - ```bash npm uninstall [<@scope>/]<pkg>... aliases: unlink, remove, rm, r, un ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/uninstall.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description This uninstalls a package, completely removing everything npm installed @@ -65,9 +56,6 @@ npm uninstall lodash --no-save ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `save` * Default: `true` unless when using `npm update` where it defaults to `false` @@ -80,9 +68,6 @@ When used with the `npm rm` command, removes the dependency from Will also prevent writing to `package-lock.json` if set to `false`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -105,9 +90,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -126,9 +108,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -142,9 +121,6 @@ the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `install-links` * Default: false @@ -154,11 +130,6 @@ When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm prune](/commands/npm-prune) diff --git a/deps/npm/docs/content/commands/npm-unpublish.md b/deps/npm/docs/content/commands/npm-unpublish.md index 9ad99e72a5a..20ef4afa947 100644 --- a/deps/npm/docs/content/commands/npm-unpublish.md +++ b/deps/npm/docs/content/commands/npm-unpublish.md @@ -6,19 +6,10 @@ description: Remove a package from the registry ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/unpublish.js --> - ```bash npm unpublish [<package-spec>] ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/unpublish.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - To learn more about how the npm registry treats unpublish, see our <a href="https://docs.npmjs.com/policies/unpublish" target="_blank" rel="noopener noreferrer"> unpublish policies</a> @@ -48,9 +39,6 @@ passed. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `dry-run` * Default: false @@ -64,9 +52,6 @@ commands that modify your local installation, eg, `install`, `update`, Note: This is NOT honored by other network related commands, eg `dist-tags`, `owner`, etc. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `force` * Default: false @@ -93,9 +78,6 @@ mistakes, unnecessary performance degradation, and malicious input. If you don't have a clear idea of what you want to do, it is strongly recommended that you do not use this option! -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -118,9 +100,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -139,11 +118,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [package spec](/using-npm/package-spec) diff --git a/deps/npm/docs/content/commands/npm-unstar.md b/deps/npm/docs/content/commands/npm-unstar.md index 636e1b6ac0a..7e49ad096a8 100644 --- a/deps/npm/docs/content/commands/npm-unstar.md +++ b/deps/npm/docs/content/commands/npm-unstar.md @@ -6,19 +6,10 @@ description: Remove an item from your favorite packages ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/unstar.js --> - ```bash npm unstar [<package-spec>...] ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/unstar.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - Note: This command is unaware of workspaces. ### Description @@ -40,9 +31,6 @@ You can see all your starred packages using [`npm stars`](/commands/npm-stars) ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `registry` * Default: "https://registry.npmjs.org/" @@ -50,9 +38,6 @@ You can see all your starred packages using [`npm stars`](/commands/npm-stars) The base URL of the npm registry. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `unicode` * Default: false on windows, true on mac/unix systems with a unicode locale, @@ -62,9 +47,6 @@ The base URL of the npm registry. When set to true, npm uses unicode characters in the tree output. When false, it uses ascii characters instead of unicode glyphs. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `otp` * Default: null @@ -76,11 +58,6 @@ when publishing or changing package permissions with `npm access`. If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm star](/commands/npm-star) diff --git a/deps/npm/docs/content/commands/npm-update.md b/deps/npm/docs/content/commands/npm-update.md index 421d04ca3dc..e18116a42dc 100644 --- a/deps/npm/docs/content/commands/npm-update.md +++ b/deps/npm/docs/content/commands/npm-update.md @@ -6,21 +6,12 @@ description: Update packages ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/update.js --> - ```bash npm update [<pkg>...] aliases: up, upgrade, udpate ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/update.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description This command will update all the packages listed to the latest version @@ -166,9 +157,6 @@ be _downgraded_. ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `save` * Default: `true` unless when using `npm update` where it defaults to `false` @@ -181,9 +169,6 @@ When used with the `npm rm` command, removes the dependency from Will also prevent writing to `package-lock.json` if set to `false`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `global` * Default: false @@ -198,9 +183,6 @@ folder instead of the current working directory. See * bin files are linked to `{prefix}/bin` * man pages are linked to `{prefix}/share/man` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `global-style` * Default: false @@ -213,9 +195,6 @@ on will be flattened in their `node_modules` folders. This obviously will eliminate some deduping. If used with `legacy-bundling`, `legacy-bundling` will be preferred. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `legacy-bundling` * Default: false @@ -226,9 +205,6 @@ such as the one included with node 0.8, can install the package. This eliminates all automatic deduping. If used with `global-style` this option will be preferred. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `omit` * Default: 'dev' if the `NODE_ENV` environment variable is set to @@ -247,9 +223,6 @@ it will be included. If the resulting omit list includes `'dev'`, then the `NODE_ENV` environment variable will be set to `'production'` for all lifecycle scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `strict-peer-deps` * Default: false @@ -269,9 +242,6 @@ When such and override is performed, a warning is printed, explaining the conflict and the packages involved. If `--strict-peer-deps` is set, then this warning is treated as a failure. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `package-lock` * Default: true @@ -282,9 +252,6 @@ will also prevent _writing_ `package-lock.json` if `save` is true. This configuration does not affect `npm ci`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `foreground-scripts` * Default: false @@ -297,9 +264,6 @@ input, output, and error with the main npm process. Note that this will generally make installs run slower, and be much noisier, but can be useful for debugging. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `ignore-scripts` * Default: false @@ -312,9 +276,6 @@ Note that commands explicitly intended to run a particular script, such as will still run their intended script if `ignore-scripts` is set, but they will *not* run any pre- or post-scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `audit` * Default: true @@ -325,9 +286,6 @@ default registry and all registries configured for scopes. See the documentation for [`npm audit`](/commands/npm-audit) for details on what is submitted. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `bin-links` * Default: true @@ -340,9 +298,6 @@ 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 --> - #### `fund` * Default: true @@ -352,9 +307,6 @@ When "true" displays the message at the end of each `npm install` acknowledging the number of dependencies looking for funding. See [`npm fund`](/commands/npm-fund) for details. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `dry-run` * Default: false @@ -368,9 +320,6 @@ commands that modify your local installation, eg, `install`, `update`, Note: This is NOT honored by other network related commands, eg `dist-tags`, `owner`, etc. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -393,9 +342,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -414,9 +360,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -430,9 +373,6 @@ the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `install-links` * Default: false @@ -442,11 +382,6 @@ When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm install](/commands/npm-install) diff --git a/deps/npm/docs/content/commands/npm-version.md b/deps/npm/docs/content/commands/npm-version.md index 8e3334d7889..9bdaf6ea65b 100644 --- a/deps/npm/docs/content/commands/npm-version.md +++ b/deps/npm/docs/content/commands/npm-version.md @@ -6,26 +6,14 @@ description: Bump a package version ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/version.js --> - ```bash npm version [<newversion> | major | minor | patch | premajor | preminor | prepatch | prerelease | from-git] alias: verison ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/version.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `allow-same-version` * Default: false @@ -34,9 +22,6 @@ alias: verison Prevents throwing an error when `npm version` is used to set the new version to the same value as the current version. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `commit-hooks` * Default: true @@ -44,9 +29,6 @@ to the same value as the current version. Run git commit hooks when using the `npm version` command. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `git-tag-version` * Default: true @@ -55,9 +37,6 @@ Run git commit hooks when using the `npm version` command. Tag the commit when using the `npm version` command. Setting this to false results in no commit being made at all. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `json` * Default: false @@ -70,9 +49,6 @@ Whether or not to output JSON data, rather than the normal output. Not supported by all npm commands. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `preid` * Default: "" @@ -81,9 +57,6 @@ Not supported by all npm commands. The "prerelease identifier" to use as a prefix for the "prerelease" part of a semver. Like the `rc` in `1.2.0-rc.8`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `sign-git-tag` * Default: false @@ -95,9 +68,6 @@ If set to true, then the `npm version` command will tag the version using Note that git requires you to have set up GPG keys in your git configs for this to work properly. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -120,9 +90,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -141,9 +108,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces-update` * Default: true @@ -152,9 +116,6 @@ This value is not exported to the environment for child processes. If set to true, the npm cli will run an update after operations that may possibly change the workspaces installed to the `node_modules` folder. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -168,11 +129,6 @@ the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### Description Run this in a package directory to bump the version and write the new data diff --git a/deps/npm/docs/content/commands/npm-view.md b/deps/npm/docs/content/commands/npm-view.md index d9d1daac0cd..bd392408ecd 100644 --- a/deps/npm/docs/content/commands/npm-view.md +++ b/deps/npm/docs/content/commands/npm-view.md @@ -6,21 +6,12 @@ description: View registry info ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/view.js --> - ```bash npm view [<package-spec>] [<field>[.subfield]...] aliases: info, show, v ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/view.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description This command shows data about a package and prints it to stdout. @@ -105,9 +96,6 @@ npm view connect versions ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `json` * Default: false @@ -120,9 +108,6 @@ Whether or not to output JSON data, rather than the normal output. Not supported by all npm commands. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -145,9 +130,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -166,9 +148,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -182,11 +161,6 @@ the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### Output If only a single string field for a single version is output, then it diff --git a/deps/npm/docs/content/commands/npm-whoami.md b/deps/npm/docs/content/commands/npm-whoami.md index 18416f633a1..3801dfaa488 100644 --- a/deps/npm/docs/content/commands/npm-whoami.md +++ b/deps/npm/docs/content/commands/npm-whoami.md @@ -6,19 +6,10 @@ description: Display npm username ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/whoami.js --> - ```bash npm whoami ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/whoami.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - Note: This command is unaware of workspaces. ### Description @@ -34,9 +25,6 @@ If logged into a registry that uses Basic Auth, then simply print the ### Configuration -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `registry` * Default: "https://registry.npmjs.org/" @@ -44,11 +32,6 @@ If logged into a registry that uses Basic Auth, then simply print the The base URL of the npm registry. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See Also * [npm config](/commands/npm-config) diff --git a/deps/npm/docs/content/commands/npm.md b/deps/npm/docs/content/commands/npm.md index 18a68d03cd4..b94e83fd8c4 100644 --- a/deps/npm/docs/content/commands/npm.md +++ b/deps/npm/docs/content/commands/npm.md @@ -6,12 +6,13 @@ description: javascript package manager ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> +```bash +npm +``` ### Version -@VERSION@ +8.19.3 ### Description diff --git a/deps/npm/docs/content/commands/npx.md b/deps/npm/docs/content/commands/npx.md index e7e59d00d84..5ce300e724b 100644 --- a/deps/npm/docs/content/commands/npx.md +++ b/deps/npm/docs/content/commands/npx.md @@ -6,10 +6,6 @@ description: Run a command from a local or remote npm package ### Synopsis -<!-- AUTOGENERATED USAGE DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/exec.js --> - ```bash npx -- <pkg>[@<version>] [args...] npx --package=<pkg>[@<version>] -- <cmd> [args...] @@ -17,11 +13,6 @@ npx -c '<cmd> [args...]' npx --package=foo -c '<cmd> [args...]' ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/commands/exec.js --> - -<!-- AUTOGENERATED USAGE DESCRIPTIONS END --> - ### Description This command allows you to run an arbitrary command from an npm package diff --git a/deps/npm/docs/content/configuring-npm/package-json.md b/deps/npm/docs/content/configuring-npm/package-json.md index 5b4acf187f7..be50e453ef4 100644 --- a/deps/npm/docs/content/configuring-npm/package-json.md +++ b/deps/npm/docs/content/configuring-npm/package-json.md @@ -18,11 +18,9 @@ settings described in [`config`](/using-npm/config). If you plan to publish your package, the *most* important things in your package.json are the name and version fields as they will be required. The name and version together form an identifier that is assumed to be -completely unique. Changes to the package should come along with changes -to the version. If you don't plan to publish your package, the name and +completely unique. If you don't plan to publish your package, the name and version fields are optional. - -The name is what your thing is called. +The name field contains your package name. Some rules: @@ -52,12 +50,9 @@ A name can be optionally prefixed by a scope, e.g. `@myorg/mypackage`. See ### version -If you plan to publish your package, the *most* important things in your -package.json are the name and version fields as they will be required. The -name and version together form an identifier that is assumed to be -completely unique. Changes to the package should come along with changes -to the version. If you don't plan to publish your package, the name and -version fields are optional. +Changes to the package should come along with changes to the version. +You can show developers how much they need to adjust on a new update by +using [semantic versioning](../../about-semantic-versioning) Version must be parseable by [node-semver](https://github.com/npm/node-semver), which is bundled with diff --git a/deps/npm/docs/content/using-npm/config.md b/deps/npm/docs/content/using-npm/config.md index cd13237f34d..d48f12eb808 100644 --- a/deps/npm/docs/content/using-npm/config.md +++ b/deps/npm/docs/content/using-npm/config.md @@ -59,9 +59,6 @@ internal to npm, and are defaults if nothing else is specified. The following shorthands are parsed on the command-line: -<!-- AUTOGENERATED CONFIG SHORTHANDS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> * `-a`: `--all` * `--enjoy-by`: `--before` * `-c`: `--call` @@ -103,10 +100,6 @@ The following shorthands are parsed on the command-line: * `--ws`: `--workspaces` * `-y`: `--yes` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> -<!-- AUTOGENERATED CONFIG SHORTHANDS END --> - If the specified configuration param resolves unambiguously to a known configuration parameter, then it is expanded to that configuration parameter. For example: @@ -130,9 +123,6 @@ npm ls --global --parseable --long --loglevel info ### Config Settings -<!-- AUTOGENERATED CONFIG DESCRIPTIONS START --> -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> #### `_auth` * Default: null @@ -146,9 +136,6 @@ Warning: This should generally not be set via a command-line option. It is safer to use a registry-provided authentication bearer token stored in the ~/.npmrc file by running `npm login`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `access` * Default: 'restricted' for scoped packages, 'public' for unscoped packages @@ -165,9 +152,6 @@ subsequent `npm publish` commands using the `--access` flag will not have an effect to the access level. To make changes to the access level after the initial publish use `npm access`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `all` * Default: false @@ -177,9 +161,6 @@ When running `npm outdated` and `npm ls`, setting `--all` will show all outdated or installed packages, rather than only those directly depended upon by the current project. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `allow-same-version` * Default: false @@ -188,9 +169,6 @@ upon by the current project. Prevents throwing an error when `npm version` is used to set the new version to the same value as the current version. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `audit` * Default: true @@ -201,9 +179,6 @@ default registry and all registries configured for scopes. See the documentation for [`npm audit`](/commands/npm-audit) for details on what is submitted. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `audit-level` * Default: null @@ -212,9 +187,6 @@ submitted. The minimum level of vulnerability for `npm audit` to exit with a non-zero exit code. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `auth-type` * Default: "legacy" @@ -225,9 +197,6 @@ removed in a future version. What authentication strategy to use with `login`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `before` * Default: null @@ -243,9 +212,6 @@ If the requested version is a `dist-tag` and the given tag does not pass the will be used. For example, `foo@latest` might install `foo@1.2` even though `latest` is `2.0`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `bin-links` * Default: true @@ -258,9 +224,6 @@ 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 --> - #### `browser` * Default: OS X: `"open"`, Windows: `"start"`, Others: `"xdg-open"` @@ -273,9 +236,6 @@ terminal. Set to `true` to use default system URL opener. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `ca` * Default: null @@ -302,9 +262,6 @@ ca[]="..." See also the `strict-ssl` config. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `cache` * Default: Windows: `%LocalAppData%\npm-cache`, Posix: `~/.npm` @@ -313,9 +270,6 @@ See also the `strict-ssl` config. The location of npm's cache directory. See [`npm cache`](/commands/npm-cache) -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `cafile` * Default: null @@ -325,9 +279,6 @@ A path to a file containing one or multiple Certificate Authority signing certificates. Similar to the `ca` setting, but allows for multiple CA's, as well as for the CA information to be stored in a file on disk. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `call` * Default: "" @@ -341,9 +292,6 @@ npm exec --package yo --package generator-node --call "yo node" ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `cert` * Default: null @@ -361,9 +309,6 @@ It is _not_ the path to a certificate file, though you can set a registry-scoped "certfile" path like "//other-registry.tld/:certfile=/path/to/cert.pem". -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `ci-name` * Default: The name of the current CI system, or `null` when not on a known CI @@ -374,9 +319,6 @@ The name of a continuous integration system. If not set explicitly, npm will detect the current CI environment using the [`@npmcli/ci-detect`](http://npm.im/@npmcli/ci-detect) module. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `cidr` * Default: null @@ -385,9 +327,6 @@ detect the current CI environment using the This is a list of CIDR address to be used when configuring limited access tokens with the `npm token create` command. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `color` * Default: true unless the NO_COLOR environ is set to something other than '0' @@ -396,9 +335,6 @@ tokens with the `npm token create` command. If false, never shows colors. If `"always"` then always shows colors. If true, then only prints color codes for tty file descriptors. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `commit-hooks` * Default: true @@ -406,9 +342,6 @@ true, then only prints color codes for tty file descriptors. Run git commit hooks when using the `npm version` command. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `depth` * Default: `Infinity` if `--all` is set, otherwise `1` @@ -419,9 +352,6 @@ The depth to go when recursing packages for `npm ls`. If not set, `npm ls` will show only the immediate dependencies of the root project. If `--all` is set, then npm will show all dependencies by default. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `description` * Default: true @@ -429,9 +359,6 @@ project. If `--all` is set, then npm will show all dependencies by default. Show the description in `npm search` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `diff` * Default: @@ -439,9 +366,6 @@ Show the description in `npm search` Define arguments to compare in `npm diff`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `diff-dst-prefix` * Default: "b/" @@ -449,9 +373,6 @@ Define arguments to compare in `npm diff`. Destination prefix to be used in `npm diff` output. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `diff-ignore-all-space` * Default: false @@ -459,9 +380,6 @@ Destination prefix to be used in `npm diff` output. Ignore whitespace when comparing lines in `npm diff`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `diff-name-only` * Default: false @@ -469,9 +387,6 @@ Ignore whitespace when comparing lines in `npm diff`. Prints only filenames when using `npm diff`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `diff-no-prefix` * Default: false @@ -482,9 +397,6 @@ Do not show any source or destination prefix in `npm diff` output. Note: this causes `npm diff` to ignore the `--diff-src-prefix` and `--diff-dst-prefix` configs. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `diff-src-prefix` * Default: "a/" @@ -492,9 +404,6 @@ Note: this causes `npm diff` to ignore the `--diff-src-prefix` and Source prefix to be used in `npm diff` output. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `diff-text` * Default: false @@ -502,9 +411,6 @@ Source prefix to be used in `npm diff` output. Treat all files as text in `npm diff`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `diff-unified` * Default: 3 @@ -512,9 +418,6 @@ Treat all files as text in `npm diff`. The number of lines of context to print in `npm diff`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `dry-run` * Default: false @@ -528,9 +431,6 @@ commands that modify your local installation, eg, `install`, `update`, Note: This is NOT honored by other network related commands, eg `dist-tags`, `owner`, etc. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `editor` * Default: The EDITOR or VISUAL environment variables, or 'notepad.exe' on @@ -539,9 +439,6 @@ Note: This is NOT honored by other network related commands, eg `dist-tags`, The command to run for `npm edit` and `npm config edit`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `engine-strict` * Default: false @@ -553,9 +450,6 @@ Node.js version. This can be overridden by setting the `--force` flag. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `fetch-retries` * Default: 2 @@ -567,9 +461,6 @@ from the registry. npm will retry idempotent read requests to the registry in the case of network failures or 5xx HTTP errors. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `fetch-retry-factor` * Default: 10 @@ -577,9 +468,6 @@ network failures or 5xx HTTP errors. The "factor" config for the `retry` module to use when fetching packages. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `fetch-retry-maxtimeout` * Default: 60000 (1 minute) @@ -588,9 +476,6 @@ The "factor" config for the `retry` module to use when fetching packages. The "maxTimeout" config for the `retry` module to use when fetching packages. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `fetch-retry-mintimeout` * Default: 10000 (10 seconds) @@ -599,9 +484,6 @@ packages. The "minTimeout" config for the `retry` module to use when fetching packages. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `fetch-timeout` * Default: 300000 (5 minutes) @@ -609,9 +491,6 @@ packages. The maximum amount of time to wait for HTTP requests to complete. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `force` * Default: false @@ -638,9 +517,6 @@ mistakes, unnecessary performance degradation, and malicious input. If you don't have a clear idea of what you want to do, it is strongly recommended that you do not use this option! -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `foreground-scripts` * Default: false @@ -653,9 +529,6 @@ input, output, and error with the main npm process. Note that this will generally make installs run slower, and be much noisier, but can be useful for debugging. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `format-package-lock` * Default: true @@ -664,9 +537,6 @@ but can be useful for debugging. Format `package-lock.json` or `npm-shrinkwrap.json` as a human readable file. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `fund` * Default: true @@ -676,9 +546,6 @@ When "true" displays the message at the end of each `npm install` acknowledging the number of dependencies looking for funding. See [`npm fund`](/commands/npm-fund) for details. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `git` * Default: "git" @@ -687,9 +554,6 @@ fund`](/commands/npm-fund) for details. The command to use for git commands. If git is installed on the computer, but is not in the `PATH`, then set this to the full path to the git binary. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `git-tag-version` * Default: true @@ -698,9 +562,6 @@ but is not in the `PATH`, then set this to the full path to the git binary. Tag the commit when using the `npm version` command. Setting this to false results in no commit being made at all. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `global` * Default: false @@ -715,9 +576,6 @@ folder instead of the current working directory. See * bin files are linked to `{prefix}/bin` * man pages are linked to `{prefix}/share/man` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `global-style` * Default: false @@ -730,9 +588,6 @@ on will be flattened in their `node_modules` folders. This obviously will eliminate some deduping. If used with `legacy-bundling`, `legacy-bundling` will be preferred. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `globalconfig` * Default: The global --prefix setting plus 'etc/npmrc'. For example, @@ -741,9 +596,6 @@ will be preferred. The config file to read for global config options. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `heading` * Default: "npm" @@ -751,9 +603,6 @@ The config file to read for global config options. The string that starts all the debugging log output. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `https-proxy` * Default: null @@ -764,9 +613,6 @@ A proxy to use for outgoing https requests. If the `HTTPS_PROXY` or proxy settings will be honored by the underlying `make-fetch-happen` library. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `if-present` * Default: false @@ -781,9 +627,6 @@ CI setup. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `ignore-scripts` * Default: false @@ -796,9 +639,6 @@ Note that commands explicitly intended to run a particular script, such as will still run their intended script if `ignore-scripts` is set, but they will *not* run any pre- or post-scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include` * Default: @@ -811,9 +651,6 @@ This is the inverse of `--omit=<type>`. Dependency types specified in `--include` will not be omitted, regardless of the order in which omit/include are specified on the command-line. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-staged` * Default: false @@ -824,9 +661,6 @@ Allow installing "staged" published packages, as defined by [npm RFC PR This is experimental, and not implemented by the npm public registry. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `include-workspace-root` * Default: false @@ -840,9 +674,6 @@ the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `init-author-email` * Default: "" @@ -850,9 +681,6 @@ This value is not exported to the environment for child processes. The value `npm init` should use by default for the package author's email. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `init-author-name` * Default: "" @@ -860,9 +688,6 @@ The value `npm init` should use by default for the package author's email. The value `npm init` should use by default for the package author's name. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `init-author-url` * Default: "" @@ -871,9 +696,6 @@ The value `npm init` should use by default for the package author's name. The value `npm init` should use by default for the package author's homepage. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `init-license` * Default: "ISC" @@ -881,9 +703,6 @@ homepage. The value `npm init` should use by default for the package license. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `init-module` * Default: "~/.npm-init.js" @@ -894,9 +713,6 @@ documentation for the [init-package-json](https://github.com/npm/init-package-json) module for more information, or [npm init](/commands/npm-init). -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `init-version` * Default: "1.0.0" @@ -905,9 +721,6 @@ more information, or [npm init](/commands/npm-init). The value that `npm init` should use by default for the package version number, if not already set in package.json. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `install-links` * Default: false @@ -917,9 +730,6 @@ When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `json` * Default: false @@ -932,9 +742,6 @@ Whether or not to output JSON data, rather than the normal output. Not supported by all npm commands. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `key` * Default: null @@ -950,9 +757,6 @@ key="-----BEGIN PRIVATE KEY-----\nXXXX\nXXXX\n-----END PRIVATE KEY-----" It is _not_ the path to a key file, though you can set a registry-scoped "keyfile" path like "//other-registry.tld/:keyfile=/path/to/key.pem". -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `legacy-bundling` * Default: false @@ -963,9 +767,6 @@ such as the one included with node 0.8, can install the package. This eliminates all automatic deduping. If used with `global-style` this option will be preferred. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `legacy-peer-deps` * Default: false @@ -984,9 +785,6 @@ This differs from `--omit=peer`, in that `--omit=peer` will avoid unpacking Use of `legacy-peer-deps` is not recommended, as it will not enforce the `peerDependencies` contract that meta-dependencies may rely on. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `link` * Default: false @@ -994,9 +792,6 @@ Use of `legacy-peer-deps` is not recommended, as it will not enforce the Used with `npm ls`, limiting output to only those packages that are linked. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `local-address` * Default: null @@ -1005,9 +800,6 @@ Used with `npm ls`, limiting output to only those packages that are linked. The IP address of the local interface to use when making connections to the npm registry. Must be IPv4 in versions of Node prior to 0.12. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `location` * Default: "user" unless `--global` is passed, which will also set this value @@ -1025,9 +817,6 @@ instead of the current working directory. See * bin files are linked to `{prefix}/bin` * man pages are linked to `{prefix}/share/man` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `lockfile-version` * Default: Version 2 if no lockfile or current lockfile version less than or @@ -1050,9 +839,6 @@ and interoperability, at the expense of more bytes on disk. disk than lockfile version 2, but not interoperable with older npm versions. Ideal if all users are on npm version 7 and higher. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `loglevel` * Default: "notice" @@ -1067,9 +853,6 @@ Any logs of a higher level than the setting are shown. The default is See also the `foreground-scripts` config. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `logs-dir` * Default: A directory named `_logs` inside the cache @@ -1078,9 +861,6 @@ See also the `foreground-scripts` config. The location of npm's log directory. See [`npm logging`](/using-npm/logging) for more information. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `logs-max` * Default: 10 @@ -1090,9 +870,6 @@ The maximum number of log files to store. If set to 0, no log files will be written for the current run. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `long` * Default: false @@ -1100,9 +877,6 @@ If set to 0, no log files will be written for the current run. Show extended information in `ls`, `search`, and `help-search`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `maxsockets` * Default: 15 @@ -1111,9 +885,6 @@ Show extended information in `ls`, `search`, and `help-search`. The maximum number of connections to use per origin (protocol/host/port combination). -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `message` * Default: "%s" @@ -1123,9 +894,6 @@ Commit message which is used by `npm version` when creating version commit. Any "%s" in the message will be replaced with the version number. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `node-options` * Default: null @@ -1135,9 +903,6 @@ Options to pass through to Node.js via the `NODE_OPTIONS` environment variable. This does not impact how npm itself is executed but it does impact how lifecycle scripts are called. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `node-version` * Default: Node.js `process.version` value @@ -1145,9 +910,6 @@ how lifecycle scripts are called. The node version to use when checking a package's `engines` setting. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `noproxy` * Default: The value of the NO_PROXY environment variable @@ -1157,9 +919,6 @@ Domain extensions that should bypass any proxies. Also accepts a comma-delimited string. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `npm-version` * Default: Output of `npm --version` @@ -1167,9 +926,6 @@ Also accepts a comma-delimited string. The npm version to use when checking a package's `engines` setting. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `offline` * Default: false @@ -1178,9 +934,6 @@ The npm version to use when checking a package's `engines` setting. Force offline mode: no network requests will be done during install. To allow the CLI to fill in missing cache data, see `--prefer-offline`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `omit` * Default: 'dev' if the `NODE_ENV` environment variable is set to @@ -1199,9 +952,6 @@ it will be included. If the resulting omit list includes `'dev'`, then the `NODE_ENV` environment variable will be set to `'production'` for all lifecycle scripts. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `omit-lockfile-registry-resolved` * Default: false @@ -1212,9 +962,6 @@ registry dependencies. Subsequent installs will need to resolve tarball endpoints with the configured registry, likely resulting in a longer install time. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `otp` * Default: null @@ -1226,9 +973,6 @@ when publishing or changing package permissions with `npm access`. If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `pack-destination` * Default: "." @@ -1236,9 +980,6 @@ password, npm will prompt on the command line for one. Directory in which `npm pack` will save tarballs. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `package` * Default: @@ -1246,9 +987,6 @@ Directory in which `npm pack` will save tarballs. The package or packages to install for [`npm exec`](/commands/npm-exec) -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `package-lock` * Default: true @@ -1259,9 +997,6 @@ will also prevent _writing_ `package-lock.json` if `save` is true. This configuration does not affect `npm ci`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `package-lock-only` * Default: false @@ -1276,9 +1011,6 @@ instead of checking `node_modules` and downloading dependencies. For `list` this means the output will be based on the tree described by the `package-lock.json`, rather than the contents of `node_modules`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `parseable` * Default: false @@ -1287,9 +1019,6 @@ For `list` this means the output will be based on the tree described by the Output parseable results from commands that write to standard output. For `npm search`, this will be tab-separated table format. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `prefer-offline` * Default: false @@ -1299,9 +1028,6 @@ If true, staleness checks for cached data will be bypassed, but missing data will be requested from the server. To force full offline mode, use `--offline`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `prefer-online` * Default: false @@ -1310,9 +1036,6 @@ will be requested from the server. To force full offline mode, use If true, staleness checks for cached data will be forced, making the CLI look for updates immediately even for fresh package data. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `prefix` * Default: In global mode, the folder where the node executable is installed. @@ -1323,9 +1046,6 @@ look for updates immediately even for fresh package data. The location to install global items. If set on the command line, then it forces non-global commands to run in the specified folder. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `preid` * Default: "" @@ -1334,9 +1054,6 @@ forces non-global commands to run in the specified folder. The "prerelease identifier" to use as a prefix for the "prerelease" part of a semver. Like the `rc` in `1.2.0-rc.8`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `progress` * Default: `true` unless running in a known CI system @@ -1347,9 +1064,6 @@ operations, if `process.stderr` is a TTY. Set to `false` to suppress the progress bar. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `proxy` * Default: null @@ -1359,9 +1073,6 @@ A proxy to use for outgoing http requests. If the `HTTP_PROXY` or `http_proxy` environment variables are set, proxy settings will be honored by the underlying `request` library. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `read-only` * Default: false @@ -1370,9 +1081,6 @@ by the underlying `request` library. This is used to mark a token as unable to publish when configuring limited access tokens with the `npm token create` command. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `rebuild-bundle` * Default: true @@ -1380,9 +1088,6 @@ access tokens with the `npm token create` command. Rebuild bundled dependencies after installation. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `registry` * Default: "https://registry.npmjs.org/" @@ -1390,9 +1095,6 @@ Rebuild bundled dependencies after installation. The base URL of the npm registry. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `replace-registry-host` * Default: "npmjs" @@ -1408,9 +1110,6 @@ registry host with the configured host every time. You may also specify a bare hostname (e.g., "registry.npmjs.org"). -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `save` * Default: `true` unless when using `npm update` where it defaults to `false` @@ -1423,9 +1122,6 @@ When used with the `npm rm` command, removes the dependency from Will also prevent writing to `package-lock.json` if set to `false`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `save-bundle` * Default: false @@ -1437,9 +1133,6 @@ If a package would be saved at install time by the use of `--save`, Ignored if `--save-peer` is set, since peerDependencies cannot be bundled. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `save-dev` * Default: false @@ -1447,9 +1140,6 @@ Ignored if `--save-peer` is set, since peerDependencies cannot be bundled. Save installed packages to a package.json file as `devDependencies`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `save-exact` * Default: false @@ -1458,9 +1148,6 @@ Save installed packages to a package.json file as `devDependencies`. Dependencies saved to package.json will be configured with an exact version rather than using npm's default semver range operator. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `save-optional` * Default: false @@ -1468,9 +1155,6 @@ rather than using npm's default semver range operator. Save installed packages to a package.json file as `optionalDependencies`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `save-peer` * Default: false @@ -1478,9 +1162,6 @@ Save installed packages to a package.json file as `optionalDependencies`. Save installed packages to a package.json file as `peerDependencies` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `save-prefix` * Default: "^" @@ -1494,9 +1175,6 @@ to `^1.2.3` which allows minor upgrades for that package, but after `npm config set save-prefix='~'` it would be set to `~1.2.3` which only allows patch upgrades. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `save-prod` * Default: false @@ -1509,9 +1187,6 @@ you want to move it to be a non-optional production dependency. This is the default behavior if `--save` is true, and neither `--save-dev` or `--save-optional` are true. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `scope` * Default: the scope of the current project, if any, or "" @@ -1542,9 +1217,6 @@ npm init --scope=@foo --yes ``` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `script-shell` * Default: '/bin/sh' on POSIX systems, 'cmd.exe' on Windows @@ -1553,9 +1225,6 @@ npm init --scope=@foo --yes The shell to use for scripts run with the `npm exec`, `npm run` and `npm init <package-spec>` commands. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `searchexclude` * Default: "" @@ -1563,9 +1232,6 @@ init <package-spec>` commands. Space-separated options that limit the results from search. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `searchlimit` * Default: 20 @@ -1574,9 +1240,6 @@ Space-separated options that limit the results from search. Number of items to limit search results to. Will not apply at all to legacy searches. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `searchopts` * Default: "" @@ -1584,9 +1247,6 @@ searches. Space-separated options that are always passed to search. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `searchstaleness` * Default: 900 @@ -1595,9 +1255,6 @@ Space-separated options that are always passed to search. The age of the cache, in seconds, before another registry request is made if using legacy search endpoint. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `shell` * Default: SHELL environment variable, or "bash" on Posix, or "cmd.exe" on @@ -1606,9 +1263,6 @@ using legacy search endpoint. The shell to run for the `npm explore` command. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `sign-git-commit` * Default: false @@ -1620,9 +1274,6 @@ version using `-S` to add a signature. Note that git requires you to have set up GPG keys in your git configs for this to work properly. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `sign-git-tag` * Default: false @@ -1634,9 +1285,6 @@ If set to true, then the `npm version` command will tag the version using Note that git requires you to have set up GPG keys in your git configs for this to work properly. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `strict-peer-deps` * Default: false @@ -1656,9 +1304,6 @@ When such and override is performed, a warning is printed, explaining the conflict and the packages involved. If `--strict-peer-deps` is set, then this warning is treated as a failure. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `strict-ssl` * Default: true @@ -1669,9 +1314,6 @@ via https. See also the `ca` config. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `tag` * Default: "latest" @@ -1686,9 +1328,6 @@ command, if no explicit tag is given. When used by the `npm diff` command, this is the tag used to fetch the tarball that will be compared with the local files by default. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `tag-version-prefix` * Default: "v" @@ -1702,9 +1341,6 @@ Because other tools may rely on the convention that npm version tags look like `v1.0.0`, _only use this property if it is absolutely necessary_. In particular, use care when overriding this setting for public packages. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `timing` * Default: false @@ -1717,9 +1353,6 @@ If true, writes a debug log to `logs-dir` and timing information to You can quickly view it with this [json](https://npm.im/json) command line: `npm exec -- json -g < ~/.npm/_timing.json`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `umask` * Default: 0 @@ -1740,9 +1373,6 @@ Thus, the effective default umask value on most POSIX systems is 0o22, meaning that folders and executables are created with a mode of 0o755 and other files are created with a mode of 0o644. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `unicode` * Default: false on windows, true on mac/unix systems with a unicode locale, @@ -1752,9 +1382,6 @@ other files are created with a mode of 0o644. When set to true, npm uses unicode characters in the tree output. When false, it uses ascii characters instead of unicode glyphs. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `update-notifier` * Default: true @@ -1763,9 +1390,6 @@ false, it uses ascii characters instead of unicode glyphs. Set to false to suppress the update notification when using an older version of npm than the latest. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `usage` * Default: false @@ -1773,9 +1397,6 @@ of npm than the latest. Show short usage output about the command specified. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `user-agent` * Default: "npm/{npm-version} node/{node-version} {platform} {arch} @@ -1794,9 +1415,6 @@ their actual counterparts: * `{ci}` - The value of the `ci-name` config, if set, prefixed with `ci/`, or an empty string if `ci-name` is empty. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `userconfig` * Default: "~/.npmrc" @@ -1808,9 +1426,6 @@ This may be overridden by the `npm_config_userconfig` environment variable or the `--userconfig` command line option, but may _not_ be overridden by settings in the `globalconfig` file. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `version` * Default: false @@ -1820,9 +1435,6 @@ If true, output the npm version and exit successfully. Only relevant when specified explicitly on the command line. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `versions` * Default: false @@ -1834,9 +1446,6 @@ exists, and exit successfully. Only relevant when specified explicitly on the command line. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `viewer` * Default: "man" on Posix, "browser" on Windows @@ -1846,9 +1455,6 @@ The program to use to view help content. Set to `"browser"` to view html help content in the default web browser. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `which` * Default: null @@ -1856,9 +1462,6 @@ Set to `"browser"` to view html help content in the default web browser. If there are multiple funding sources, which 1-indexed source URL to open. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspace` * Default: @@ -1881,9 +1484,6 @@ brand new workspace within the project. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces` * Default: null @@ -1902,9 +1502,6 @@ _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `workspaces-update` * Default: true @@ -1913,9 +1510,6 @@ This value is not exported to the environment for child processes. If set to true, the npm cli will run an update after operations that may possibly change the workspaces installed to the `node_modules` folder. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `yes` * Default: null @@ -1924,9 +1518,6 @@ possibly change the workspaces installed to the `node_modules` folder. Automatically answer "yes" to any prompts that npm might print on the command line. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `also` * Default: null @@ -1935,9 +1526,6 @@ command line. When set to `dev` or `development`, this is an alias for `--include=dev`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `cache-max` * Default: Infinity @@ -1946,9 +1534,6 @@ When set to `dev` or `development`, this is an alias for `--include=dev`. `--cache-max=0` is an alias for `--prefer-online` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `cache-min` * Default: 0 @@ -1957,9 +1542,6 @@ When set to `dev` or `development`, this is an alias for `--include=dev`. `--cache-min=9999 (or bigger)` is an alias for `--prefer-offline`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `dev` * Default: false @@ -1968,9 +1550,6 @@ When set to `dev` or `development`, this is an alias for `--include=dev`. Alias for `--include=dev`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `init.author.email` * Default: "" @@ -1979,9 +1558,6 @@ Alias for `--include=dev`. Alias for `--init-author-email` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `init.author.name` * Default: "" @@ -1990,9 +1566,6 @@ Alias for `--init-author-email` Alias for `--init-author-name` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `init.author.url` * Default: "" @@ -2001,9 +1574,6 @@ Alias for `--init-author-name` Alias for `--init-author-url` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `init.license` * Default: "ISC" @@ -2012,9 +1582,6 @@ Alias for `--init-author-url` Alias for `--init-license` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `init.module` * Default: "~/.npm-init.js" @@ -2023,9 +1590,6 @@ Alias for `--init-license` Alias for `--init-module` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `init.version` * Default: "1.0.0" @@ -2034,9 +1598,6 @@ Alias for `--init-module` Alias for `--init-version` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `only` * Default: null @@ -2045,9 +1606,6 @@ Alias for `--init-version` When set to `prod` or `production`, this is an alias for `--omit=dev`. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `optional` * Default: null @@ -2059,9 +1617,6 @@ Default value does install optional deps unless otherwise omitted. Alias for --include=optional or --omit=optional -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `production` * Default: null @@ -2070,9 +1625,6 @@ Alias for --include=optional or --omit=optional Alias for `--omit=dev` -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `shrinkwrap` * Default: true @@ -2081,9 +1633,6 @@ Alias for `--omit=dev` Alias for --package-lock -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `sso-poll-frequency` * Default: 500 @@ -2094,9 +1643,6 @@ Alias for --package-lock When used with SSO-enabled `auth-type`s, configures how regularly the registry should be polled while the user is completing authentication. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `sso-type` * Default: "oauth" @@ -2106,9 +1652,6 @@ registry should be polled while the user is completing authentication. If `--auth-type=sso`, the type of SSO type to use. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> - #### `tmp` * Default: The value returned by the Node.js `os.tmpdir()` method @@ -2121,10 +1664,6 @@ If `--auth-type=sso`, the type of SSO type to use. Historically, the location where temporary files were stored. No longer relevant. -<!-- automatically generated, do not edit manually --> -<!-- see lib/utils/config/definitions.js --> -<!-- AUTOGENERATED CONFIG DESCRIPTIONS END --> - ### See also * [npm config](/commands/npm-config) diff --git a/deps/npm/docs/content/using-npm/package-spec.md b/deps/npm/docs/content/using-npm/package-spec.md index 0d3741018f0..fd64131fbc4 100644 --- a/deps/npm/docs/content/using-npm/package-spec.md +++ b/deps/npm/docs/content/using-npm/package-spec.md @@ -4,7 +4,6 @@ section: 7 description: Package name specifier --- - ### Description Commands like `npm install` and the dependency sections in the diff --git a/deps/npm/docs/output/commands/npm-access.html b/deps/npm/docs/output/commands/npm-access.html index 57d17abbd8f..211f0c24fd0 100644 --- a/deps/npm/docs/output/commands/npm-access.html +++ b/deps/npm/docs/output/commands/npm-access.html @@ -146,9 +146,6 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm access public [<package>] npm access restricted [<package>] npm access grant <read-only|read-write> <scope:team> [<package>] @@ -159,9 +156,6 @@ npm access ls-packages [<user>|<scope>|<scope:team>] npm access ls-collaborators [<package> [<user>]] npm access edit [<package>] </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>Used to set access controls on private packages.</p> <p>For all of the subcommands, <code>npm access</code> will perform actions on the packages @@ -220,17 +214,12 @@ fail with an HTTP 402 status code (logically enough), unless you use <code>--access=public</code>.</p> <p>Management of teams and team memberships is done with the <code>npm team</code> command.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="registry"><code>registry</code></h4> <ul> <li>Default: "<a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a>"</li> <li>Type: URL</li> </ul> <p>The base URL of the npm registry.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="otp"><code>otp</code></h4> <ul> <li>Default: null</li> @@ -240,9 +229,6 @@ fail with an HTTP 402 status code (logically enough), unless you use when publishing or changing package permissions with <code>npm access</code>.</p> <p>If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="https://npm.im/libnpmaccess"><code>libnpmaccess</code></a></li> diff --git a/deps/npm/docs/output/commands/npm-adduser.html b/deps/npm/docs/output/commands/npm-adduser.html index d084a5e1f2d..7592e2ecc38 100644 --- a/deps/npm/docs/output/commands/npm-adduser.html +++ b/deps/npm/docs/output/commands/npm-adduser.html @@ -146,16 +146,10 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm adduser aliases: login, add-user </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>Note: This command is unaware of workspaces.</p> <h3 id="description">Description</h3> <p>Create or verify a user named <code><username></code> in the specified registry, and @@ -170,17 +164,12 @@ the username, password and email address must all match with your existing record.</p> <p><code>npm login</code> is an alias to <code>adduser</code> and behaves exactly the same way.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="registry"><code>registry</code></h4> <ul> <li>Default: "<a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a>"</li> <li>Type: URL</li> </ul> <p>The base URL of the npm registry.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="scope"><code>scope</code></h4> <ul> <li>Default: the scope of the current project, if any, or ""</li> @@ -202,8 +191,6 @@ installation of packages specified according to the pattern # instead of just named "whatever" npm init --scope=@foo --yes </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="auth-type"><code>auth-type</code></h4> <ul> <li>Default: "legacy"</li> @@ -212,9 +199,6 @@ npm init --scope=@foo --yes <p>NOTE: auth-type values "sso", "saml", "oauth", and "webauthn" will be removed in a future version.</p> <p>What authentication strategy to use with <code>login</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../using-npm/registry.html">npm registry</a></li> diff --git a/deps/npm/docs/output/commands/npm-audit.html b/deps/npm/docs/output/commands/npm-audit.html index fa2c4ad52bc..c5961a814fe 100644 --- a/deps/npm/docs/output/commands/npm-audit.html +++ b/deps/npm/docs/output/commands/npm-audit.html @@ -146,14 +146,8 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm audit [fix|signatures] </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>The audit command submits a description of the dependencies configured in your project to your default registry and asks for a report of known @@ -314,9 +308,6 @@ fixing anything:</p> <pre lang="bash"><code>$ npm audit --audit-level=moderate </code></pre> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="audit-level"><code>audit-level</code></h4> <ul> <li>Default: null</li> @@ -324,8 +315,6 @@ fixing anything:</p> </ul> <p>The minimum level of vulnerability for <code>npm audit</code> to exit with a non-zero exit code.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="dry-run"><code>dry-run</code></h4> <ul> <li>Default: false</li> @@ -337,8 +326,6 @@ commands that modify your local installation, eg, <code>install</code>, <code>up <code>dedupe</code>, <code>uninstall</code>, as well as <code>pack</code> and <code>publish</code>.</p> <p>Note: This is NOT honored by other network related commands, eg <code>dist-tags</code>, <code>owner</code>, etc.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="force"><code>force</code></h4> <ul> <li>Default: false</li> @@ -364,8 +351,6 @@ range (including SemVer-major changes).</li> </ul> <p>If you don't have a clear idea of what you want to do, it is strongly recommended that you do not use this option!</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="json"><code>json</code></h4> <ul> <li>Default: false</li> @@ -377,8 +362,6 @@ recommended that you do not use this option!</p> saving them to your <code>package.json</code>.</li> </ul> <p>Not supported by all npm commands.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="package-lock-only"><code>package-lock-only</code></h4> <ul> <li>Default: false</li> @@ -390,8 +373,6 @@ ignoring <code>node_modules</code>.</p> instead of checking <code>node_modules</code> and downloading dependencies.</p> <p>For <code>list</code> this means the output will be based on the tree described by the <code>package-lock.json</code>, rather than the contents of <code>node_modules</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="omit"><code>omit</code></h4> <ul> <li>Default: 'dev' if the <code>NODE_ENV</code> environment variable is set to @@ -406,8 +387,6 @@ physically installed on disk.</p> it will be included.</p> <p>If the resulting omit list includes <code>'dev'</code>, then the <code>NODE_ENV</code> environment variable will be set to <code>'production'</code> for all lifecycle scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="foreground-scripts"><code>foreground-scripts</code></h4> <ul> <li>Default: false</li> @@ -418,8 +397,6 @@ scripts for installed packages in the foreground process, sharing standard input, output, and error with the main npm process.</p> <p>Note that this will generally make installs run slower, and be much noisier, but can be useful for debugging.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="ignore-scripts"><code>ignore-scripts</code></h4> <ul> <li>Default: false</li> @@ -430,8 +407,6 @@ but can be useful for debugging.</p> <code>npm start</code>, <code>npm stop</code>, <code>npm restart</code>, <code>npm test</code>, and <code>npm run-script</code> will still run their intended script if <code>ignore-scripts</code> is set, but they will <em>not</em> run any pre- or post-scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -451,8 +426,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -469,8 +442,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -481,8 +452,6 @@ other things (test, exec, publish, etc.) will operate on the root project, all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="install-links"><code>install-links</code></h4> <ul> <li>Default: false</li> @@ -491,9 +460,6 @@ the specified workspaces, and not on the root project.</p> <p>When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-install.html">npm install</a></li> diff --git a/deps/npm/docs/output/commands/npm-bin.html b/deps/npm/docs/output/commands/npm-bin.html index 5961ea7e50f..3d219ce4121 100644 --- a/deps/npm/docs/output/commands/npm-bin.html +++ b/deps/npm/docs/output/commands/npm-bin.html @@ -146,21 +146,12 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm bin </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>Note: This command is unaware of workspaces.</p> <h3 id="description">Description</h3> <p>Print the folder where npm will install executables.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="global"><code>global</code></h4> <ul> <li>Default: false</li> @@ -175,9 +166,6 @@ of the current working directory.</li> <li>bin files are linked to <code>{prefix}/bin</code></li> <li>man pages are linked to <code>{prefix}/share/man</code></li> </ul> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-prefix.html">npm prefix</a></li> diff --git a/deps/npm/docs/output/commands/npm-bugs.html b/deps/npm/docs/output/commands/npm-bugs.html index 28fdc0c6438..a14305c7e99 100644 --- a/deps/npm/docs/output/commands/npm-bugs.html +++ b/deps/npm/docs/output/commands/npm-bugs.html @@ -146,25 +146,16 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm bugs [<pkgname> [<pkgname> ...]] alias: issues </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>This command tries to guess at the likely location of a package's bug tracker URL or the <code>mailto</code> URL of the support email, and then tries to open it using the <code>--browser</code> config param. If no package name is provided, it will search for a <code>package.json</code> in the current folder and use the <code>name</code> property.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="browser"><code>browser</code></h4> <ul> <li>Default: OS X: <code>"open"</code>, Windows: <code>"start"</code>, Others: <code>"xdg-open"</code></li> @@ -174,16 +165,12 @@ will search for a <code>package.json</code> in the current folder and use the <c <p>Set to <code>false</code> to suppress browser behavior and instead print urls to terminal.</p> <p>Set to <code>true</code> to use default system URL opener.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="registry"><code>registry</code></h4> <ul> <li>Default: "<a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a>"</li> <li>Type: URL</li> </ul> <p>The base URL of the npm registry.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -203,8 +190,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -221,8 +206,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -233,9 +216,6 @@ other things (test, exec, publish, etc.) will operate on the root project, all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-docs.html">npm docs</a></li> diff --git a/deps/npm/docs/output/commands/npm-cache.html b/deps/npm/docs/output/commands/npm-cache.html index ad29cc73819..a9409a4b216 100644 --- a/deps/npm/docs/output/commands/npm-cache.html +++ b/deps/npm/docs/output/commands/npm-cache.html @@ -146,17 +146,11 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm cache add <package-spec> npm cache clean [<key>] npm cache ls [<name>@<version>] npm cache verify </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>Note: This command is unaware of workspaces.</p> <h3 id="description">Description</h3> <p>Used to add, list, or clean the npm cache folder.</p> @@ -206,18 +200,12 @@ cache makes is that, if it does return data, that data will be exactly the data that was inserted.</p> <p>To run an offline verification of existing cache contents, use <code>npm cache verify</code>.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="cache"><code>cache</code></h4> <ul> <li>Default: Windows: <code>%LocalAppData%\npm-cache</code>, Posix: <code>~/.npm</code></li> <li>Type: Path</li> </ul> <p>The location of npm's cache directory. See <a href="../commands/npm-cache.html"><code>npm cache</code></a></p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../using-npm/package-spec.html">package spec</a></li> diff --git a/deps/npm/docs/output/commands/npm-ci.html b/deps/npm/docs/output/commands/npm-ci.html index a67ad8237e7..63d22471cd2 100644 --- a/deps/npm/docs/output/commands/npm-ci.html +++ b/deps/npm/docs/output/commands/npm-ci.html @@ -146,16 +146,10 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm ci aliases: clean-install, ic, install-clean, isntall-clean </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>This command is similar to <a href="../commands/npm-install.html"><code>npm install</code></a>, except it's meant to be used in automated environments such as test platforms, @@ -202,9 +196,6 @@ cache: - "$HOME/.npm" </code></pre> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="save"><code>save</code></h4> <ul> <li>Default: <code>true</code> unless when using <code>npm update</code> where it defaults to <code>false</code></li> @@ -214,8 +205,6 @@ cache: <p>When used with the <code>npm rm</code> command, removes the dependency from <code>package.json</code>.</p> <p>Will also prevent writing to <code>package-lock.json</code> if set to <code>false</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="save-exact"><code>save-exact</code></h4> <ul> <li>Default: false</li> @@ -223,8 +212,6 @@ cache: </ul> <p>Dependencies saved to package.json will be configured with an exact version rather than using npm's default semver range operator.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="global"><code>global</code></h4> <ul> <li>Default: false</li> @@ -239,8 +226,6 @@ of the current working directory.</li> <li>bin files are linked to <code>{prefix}/bin</code></li> <li>man pages are linked to <code>{prefix}/share/man</code></li> </ul> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="global-style"><code>global-style</code></h4> <ul> <li>Default: false</li> @@ -252,8 +237,6 @@ direct dependencies will show in <code>node_modules</code> and everything they d on will be flattened in their <code>node_modules</code> folders. This obviously will eliminate some deduping. If used with <code>legacy-bundling</code>, <code>legacy-bundling</code> will be preferred.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="legacy-bundling"><code>legacy-bundling</code></h4> <ul> <li>Default: false</li> @@ -263,8 +246,6 @@ will be preferred.</p> such as the one included with node 0.8, can install the package. This eliminates all automatic deduping. If used with <code>global-style</code> this option will be preferred.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="omit"><code>omit</code></h4> <ul> <li>Default: 'dev' if the <code>NODE_ENV</code> environment variable is set to @@ -279,8 +260,6 @@ physically installed on disk.</p> it will be included.</p> <p>If the resulting omit list includes <code>'dev'</code>, then the <code>NODE_ENV</code> environment variable will be set to <code>'production'</code> for all lifecycle scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="strict-peer-deps"><code>strict-peer-deps</code></h4> <ul> <li>Default: false</li> @@ -297,8 +276,6 @@ the range set in their package's <code>peerDependencies</code> object.</p> <p>When such and override is performed, a warning is printed, explaining the conflict and the packages involved. If <code>--strict-peer-deps</code> is set, then this warning is treated as a failure.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="package-lock"><code>package-lock</code></h4> <ul> <li>Default: true</li> @@ -307,8 +284,6 @@ this warning is treated as a failure.</p> <p>If set to false, then ignore <code>package-lock.json</code> files when installing. This will also prevent <em>writing</em> <code>package-lock.json</code> if <code>save</code> is true.</p> <p>This configuration does not affect <code>npm ci</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="foreground-scripts"><code>foreground-scripts</code></h4> <ul> <li>Default: false</li> @@ -319,8 +294,6 @@ scripts for installed packages in the foreground process, sharing standard input, output, and error with the main npm process.</p> <p>Note that this will generally make installs run slower, and be much noisier, but can be useful for debugging.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="ignore-scripts"><code>ignore-scripts</code></h4> <ul> <li>Default: false</li> @@ -331,8 +304,6 @@ but can be useful for debugging.</p> <code>npm start</code>, <code>npm stop</code>, <code>npm restart</code>, <code>npm test</code>, and <code>npm run-script</code> will still run their intended script if <code>ignore-scripts</code> is set, but they will <em>not</em> run any pre- or post-scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="audit"><code>audit</code></h4> <ul> <li>Default: true</li> @@ -342,8 +313,6 @@ will <em>not</em> run any pre- or post-scripts.</p> default registry and all registries configured for scopes. See the documentation for <a href="../commands/npm-audit.html"><code>npm audit</code></a> for details on what is submitted.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="bin-links"><code>bin-links</code></h4> <ul> <li>Default: true</li> @@ -354,8 +323,6 @@ executables.</p> <p>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.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="fund"><code>fund</code></h4> <ul> <li>Default: true</li> @@ -363,8 +330,6 @@ systems.</p> </ul> <p>When "true" displays the message at the end of each <code>npm install</code> acknowledging the number of dependencies looking for funding. See <a href="../commands/npm-fund.html"><code>npm fund</code></a> for details.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="dry-run"><code>dry-run</code></h4> <ul> <li>Default: false</li> @@ -376,8 +341,6 @@ commands that modify your local installation, eg, <code>install</code>, <code>up <code>dedupe</code>, <code>uninstall</code>, as well as <code>pack</code> and <code>publish</code>.</p> <p>Note: This is NOT honored by other network related commands, eg <code>dist-tags</code>, <code>owner</code>, etc.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -397,8 +360,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -415,8 +376,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -427,8 +386,6 @@ other things (test, exec, publish, etc.) will operate on the root project, all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="install-links"><code>install-links</code></h4> <ul> <li>Default: false</li> @@ -437,9 +394,6 @@ the specified workspaces, and not on the root project.</p> <p>When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-install.html">npm install</a></li> diff --git a/deps/npm/docs/output/commands/npm-completion.html b/deps/npm/docs/output/commands/npm-completion.html index 3864e693bd9..a9a991b28c2 100644 --- a/deps/npm/docs/output/commands/npm-completion.html +++ b/deps/npm/docs/output/commands/npm-completion.html @@ -146,14 +146,8 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm completion </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>Note: This command is unaware of workspaces.</p> <h3 id="description">Description</h3> <p>Enables tab-completion in all npm commands.</p> diff --git a/deps/npm/docs/output/commands/npm-config.html b/deps/npm/docs/output/commands/npm-config.html index 184895e036f..d01a59f95cc 100644 --- a/deps/npm/docs/output/commands/npm-config.html +++ b/deps/npm/docs/output/commands/npm-config.html @@ -146,9 +146,6 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm config set <key>=<value> [<key>=<value> ...] npm config get [<key> [<key> ...]] npm config delete <key> [<key> ...] @@ -157,9 +154,6 @@ npm config edit alias: c </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>Note: This command is unaware of workspaces.</p> <h3 id="description">Description</h3> <p>npm gets its config settings from the command line, environment @@ -203,9 +197,6 @@ to show the settings in json format.</p> <p>Opens the config file in an editor. Use the <code>--global</code> flag to edit the global config.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="json"><code>json</code></h4> <ul> <li>Default: false</li> @@ -217,8 +208,6 @@ global config.</p> saving them to your <code>package.json</code>.</li> </ul> <p>Not supported by all npm commands.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="global"><code>global</code></h4> <ul> <li>Default: false</li> @@ -233,8 +222,6 @@ of the current working directory.</li> <li>bin files are linked to <code>{prefix}/bin</code></li> <li>man pages are linked to <code>{prefix}/share/man</code></li> </ul> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="editor"><code>editor</code></h4> <ul> <li>Default: The EDITOR or VISUAL environment variables, or 'notepad.exe' on @@ -242,8 +229,6 @@ Windows, or 'vim' on Unix systems</li> <li>Type: String</li> </ul> <p>The command to run for <code>npm edit</code> and <code>npm config edit</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="location"><code>location</code></h4> <ul> <li>Default: "user" unless <code>--global</code> is passed, which will also set this value @@ -260,17 +245,12 @@ of the current working directory.</li> <li>bin files are linked to <code>{prefix}/bin</code></li> <li>man pages are linked to <code>{prefix}/share/man</code></li> </ul> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="long"><code>long</code></h4> <ul> <li>Default: false</li> <li>Type: Boolean</li> </ul> <p>Show extended information in <code>ls</code>, <code>search</code>, and <code>help-search</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../configuring-npm/folders.html">npm folders</a></li> diff --git a/deps/npm/docs/output/commands/npm-dedupe.html b/deps/npm/docs/output/commands/npm-dedupe.html index 89d62caf702..49f37ca7d88 100644 --- a/deps/npm/docs/output/commands/npm-dedupe.html +++ b/deps/npm/docs/output/commands/npm-dedupe.html @@ -146,16 +146,10 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm dedupe alias: ddp </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>Searches the local package tree and attempts to simplify the overall structure by moving dependencies further up the tree, where they can @@ -201,9 +195,6 @@ result in new modules being installed.</p> dependencies in your project <code>package.json</code>, if you want to update values in <code>package.json</code> you can run: <code>npm update --save</code> instead.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="global-style"><code>global-style</code></h4> <ul> <li>Default: false</li> @@ -215,8 +206,6 @@ direct dependencies will show in <code>node_modules</code> and everything they d on will be flattened in their <code>node_modules</code> folders. This obviously will eliminate some deduping. If used with <code>legacy-bundling</code>, <code>legacy-bundling</code> will be preferred.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="legacy-bundling"><code>legacy-bundling</code></h4> <ul> <li>Default: false</li> @@ -226,8 +215,6 @@ will be preferred.</p> such as the one included with node 0.8, can install the package. This eliminates all automatic deduping. If used with <code>global-style</code> this option will be preferred.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="strict-peer-deps"><code>strict-peer-deps</code></h4> <ul> <li>Default: false</li> @@ -244,8 +231,6 @@ the range set in their package's <code>peerDependencies</code> object.</p> <p>When such and override is performed, a warning is printed, explaining the conflict and the packages involved. If <code>--strict-peer-deps</code> is set, then this warning is treated as a failure.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="package-lock"><code>package-lock</code></h4> <ul> <li>Default: true</li> @@ -254,8 +239,6 @@ this warning is treated as a failure.</p> <p>If set to false, then ignore <code>package-lock.json</code> files when installing. This will also prevent <em>writing</em> <code>package-lock.json</code> if <code>save</code> is true.</p> <p>This configuration does not affect <code>npm ci</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="omit"><code>omit</code></h4> <ul> <li>Default: 'dev' if the <code>NODE_ENV</code> environment variable is set to @@ -270,8 +253,6 @@ physically installed on disk.</p> it will be included.</p> <p>If the resulting omit list includes <code>'dev'</code>, then the <code>NODE_ENV</code> environment variable will be set to <code>'production'</code> for all lifecycle scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="ignore-scripts"><code>ignore-scripts</code></h4> <ul> <li>Default: false</li> @@ -282,8 +263,6 @@ variable will be set to <code>'production'</code> for all lifecycle scripts.</p> <code>npm start</code>, <code>npm stop</code>, <code>npm restart</code>, <code>npm test</code>, and <code>npm run-script</code> will still run their intended script if <code>ignore-scripts</code> is set, but they will <em>not</em> run any pre- or post-scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="audit"><code>audit</code></h4> <ul> <li>Default: true</li> @@ -293,8 +272,6 @@ will <em>not</em> run any pre- or post-scripts.</p> default registry and all registries configured for scopes. See the documentation for <a href="../commands/npm-audit.html"><code>npm audit</code></a> for details on what is submitted.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="bin-links"><code>bin-links</code></h4> <ul> <li>Default: true</li> @@ -305,8 +282,6 @@ executables.</p> <p>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.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="fund"><code>fund</code></h4> <ul> <li>Default: true</li> @@ -314,8 +289,6 @@ systems.</p> </ul> <p>When "true" displays the message at the end of each <code>npm install</code> acknowledging the number of dependencies looking for funding. See <a href="../commands/npm-fund.html"><code>npm fund</code></a> for details.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="dry-run"><code>dry-run</code></h4> <ul> <li>Default: false</li> @@ -327,8 +300,6 @@ commands that modify your local installation, eg, <code>install</code>, <code>up <code>dedupe</code>, <code>uninstall</code>, as well as <code>pack</code> and <code>publish</code>.</p> <p>Note: This is NOT honored by other network related commands, eg <code>dist-tags</code>, <code>owner</code>, etc.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -348,8 +319,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -366,8 +335,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -378,8 +345,6 @@ other things (test, exec, publish, etc.) will operate on the root project, all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="install-links"><code>install-links</code></h4> <ul> <li>Default: false</li> @@ -388,9 +353,6 @@ the specified workspaces, and not on the root project.</p> <p>When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-find-dupes.html">npm find-dupes</a></li> diff --git a/deps/npm/docs/output/commands/npm-deprecate.html b/deps/npm/docs/output/commands/npm-deprecate.html index 5b1d3489ca6..252942841da 100644 --- a/deps/npm/docs/output/commands/npm-deprecate.html +++ b/deps/npm/docs/output/commands/npm-deprecate.html @@ -146,14 +146,8 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm deprecate <package-spec> <message> </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>Note: This command is unaware of workspaces.</p> <h3 id="description">Description</h3> <p>This command will update the npm registry entry for a package, providing a @@ -173,17 +167,12 @@ include prerelease versions. For example:</p> argument. Note that you must use double quotes with no space between them to format an empty string.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="registry"><code>registry</code></h4> <ul> <li>Default: "<a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a>"</li> <li>Type: URL</li> </ul> <p>The base URL of the npm registry.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="otp"><code>otp</code></h4> <ul> <li>Default: null</li> @@ -193,9 +182,6 @@ format an empty string.</p> when publishing or changing package permissions with <code>npm access</code>.</p> <p>If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../using-npm/package-spec.html">package spec</a></li> diff --git a/deps/npm/docs/output/commands/npm-diff.html b/deps/npm/docs/output/commands/npm-diff.html index 13ed989c461..db9a23d27cb 100644 --- a/deps/npm/docs/output/commands/npm-diff.html +++ b/deps/npm/docs/output/commands/npm-diff.html @@ -146,14 +146,8 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm diff [...<paths>] </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>Similar to its <code>git diff</code> counterpart, this command will print diff patches of files for packages published to the npm registry.</p> @@ -261,41 +255,30 @@ of files for a given package, e.g:</p> located within the folder <code>./lib/</code> and changed lines of code within the <code>CHANGELOG.md</code> file.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="diff"><code>diff</code></h4> <ul> <li>Default:</li> <li>Type: String (can be set multiple times)</li> </ul> <p>Define arguments to compare in <code>npm diff</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="diff-name-only"><code>diff-name-only</code></h4> <ul> <li>Default: false</li> <li>Type: Boolean</li> </ul> <p>Prints only filenames when using <code>npm diff</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="diff-unified"><code>diff-unified</code></h4> <ul> <li>Default: 3</li> <li>Type: Number</li> </ul> <p>The number of lines of context to print in <code>npm diff</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="diff-ignore-all-space"><code>diff-ignore-all-space</code></h4> <ul> <li>Default: false</li> <li>Type: Boolean</li> </ul> <p>Ignore whitespace when comparing lines in <code>npm diff</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="diff-no-prefix"><code>diff-no-prefix</code></h4> <ul> <li>Default: false</li> @@ -304,32 +287,24 @@ located within the folder <code>./lib/</code> and changed lines of code within t <p>Do not show any source or destination prefix in <code>npm diff</code> output.</p> <p>Note: this causes <code>npm diff</code> to ignore the <code>--diff-src-prefix</code> and <code>--diff-dst-prefix</code> configs.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="diff-src-prefix"><code>diff-src-prefix</code></h4> <ul> <li>Default: "a/"</li> <li>Type: String</li> </ul> <p>Source prefix to be used in <code>npm diff</code> output.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="diff-dst-prefix"><code>diff-dst-prefix</code></h4> <ul> <li>Default: "b/"</li> <li>Type: String</li> </ul> <p>Destination prefix to be used in <code>npm diff</code> output.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="diff-text"><code>diff-text</code></h4> <ul> <li>Default: false</li> <li>Type: Boolean</li> </ul> <p>Treat all files as text in <code>npm diff</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="global"><code>global</code></h4> <ul> <li>Default: false</li> @@ -344,8 +319,6 @@ of the current working directory.</li> <li>bin files are linked to <code>{prefix}/bin</code></li> <li>man pages are linked to <code>{prefix}/share/man</code></li> </ul> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="tag"><code>tag</code></h4> <ul> <li>Default: "latest"</li> @@ -357,8 +330,6 @@ then it will install the specified tag.</p> command, if no explicit tag is given.</p> <p>When used by the <code>npm diff</code> command, this is the tag used to fetch the tarball that will be compared with the local files by default.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -378,8 +349,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -396,8 +365,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -408,9 +375,6 @@ other things (test, exec, publish, etc.) will operate on the root project, all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h2 id="see-also">See Also</h2> <ul> <li><a href="../commands/npm-outdated.html">npm outdated</a></li> diff --git a/deps/npm/docs/output/commands/npm-dist-tag.html b/deps/npm/docs/output/commands/npm-dist-tag.html index a6cdc6230b2..31ecd3c96c8 100644 --- a/deps/npm/docs/output/commands/npm-dist-tag.html +++ b/deps/npm/docs/output/commands/npm-dist-tag.html @@ -146,18 +146,12 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm dist-tag add <package-spec (with version)> [<tag>] npm dist-tag rm <package-spec> <tag> npm dist-tag ls [<package-spec>] alias: dist-tags </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>Add, remove, and enumerate distribution tags on a package:</p> <ul> @@ -216,9 +210,6 @@ semver as <code>>=1.4.0 <1.5.0</code>. See <a href="https://github.com/np <p>The simplest way to avoid semver problems with tags is to use tags that do not begin with a number or the letter <code>v</code>.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -238,8 +229,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -256,8 +245,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -268,9 +255,6 @@ other things (test, exec, publish, etc.) will operate on the root project, all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../using-npm/package-spec.html">package spec</a></li> diff --git a/deps/npm/docs/output/commands/npm-docs.html b/deps/npm/docs/output/commands/npm-docs.html index 8155100d225..3f3769f30c9 100644 --- a/deps/npm/docs/output/commands/npm-docs.html +++ b/deps/npm/docs/output/commands/npm-docs.html @@ -146,16 +146,10 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm docs [<pkgname> [<pkgname> ...]] alias: home </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>This command tries to guess at the likely location of a package's documentation URL, and then tries to open it using the <code>--browser</code> config @@ -163,9 +157,6 @@ param. You can pass multiple package names at once. If no package name is provided, it will search for a <code>package.json</code> in the current folder and use the <code>name</code> property.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="browser"><code>browser</code></h4> <ul> <li>Default: OS X: <code>"open"</code>, Windows: <code>"start"</code>, Others: <code>"xdg-open"</code></li> @@ -175,16 +166,12 @@ the <code>name</code> property.</p> <p>Set to <code>false</code> to suppress browser behavior and instead print urls to terminal.</p> <p>Set to <code>true</code> to use default system URL opener.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="registry"><code>registry</code></h4> <ul> <li>Default: "<a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a>"</li> <li>Type: URL</li> </ul> <p>The base URL of the npm registry.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -204,8 +191,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -222,8 +207,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -234,9 +217,6 @@ other things (test, exec, publish, etc.) will operate on the root project, all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-view.html">npm view</a></li> diff --git a/deps/npm/docs/output/commands/npm-doctor.html b/deps/npm/docs/output/commands/npm-doctor.html index 1d41b2ce186..a3e58972d8c 100644 --- a/deps/npm/docs/output/commands/npm-doctor.html +++ b/deps/npm/docs/output/commands/npm-doctor.html @@ -146,14 +146,8 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm doctor </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>Note: This command is unaware of workspaces.</p> <h3 id="description">Description</h3> <p><code>npm doctor</code> runs a set of checks to ensure that your npm installation has @@ -229,18 +223,12 @@ located with <code>npm config get cache</code>). In the event that there are cor packages in your cache, you should probably run <code>npm cache clean -f</code> and reset the cache.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="registry"><code>registry</code></h4> <ul> <li>Default: "<a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a>"</li> <li>Type: URL</li> </ul> <p>The base URL of the npm registry.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-bugs.html">npm bugs</a></li> diff --git a/deps/npm/docs/output/commands/npm-edit.html b/deps/npm/docs/output/commands/npm-edit.html index 78c2445fa10..8f4fd07614b 100644 --- a/deps/npm/docs/output/commands/npm-edit.html +++ b/deps/npm/docs/output/commands/npm-edit.html @@ -146,14 +146,8 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm edit <pkg>[/<subpkg>...] </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>Note: This command is unaware of workspaces.</p> <h3 id="description">Description</h3> <p>Selects a dependency in the current project and opens the package folder in @@ -165,9 +159,6 @@ changes in compiled packages.</p> into your package, and then <code>npm edit connect</code> to make a few changes to your locally installed copy.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="editor"><code>editor</code></h4> <ul> <li>Default: The EDITOR or VISUAL environment variables, or 'notepad.exe' on @@ -175,9 +166,6 @@ Windows, or 'vim' on Unix systems</li> <li>Type: String</li> </ul> <p>The command to run for <code>npm edit</code> and <code>npm config edit</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../configuring-npm/folders.html">npm folders</a></li> diff --git a/deps/npm/docs/output/commands/npm-exec.html b/deps/npm/docs/output/commands/npm-exec.html index 917d71db366..c30e5349568 100644 --- a/deps/npm/docs/output/commands/npm-exec.html +++ b/deps/npm/docs/output/commands/npm-exec.html @@ -146,9 +146,6 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm exec -- <pkg>[@<version>] [args...] npm exec --package=<pkg>[@<version>] -- <cmd> [args...] npm exec -c '<cmd> [args...]' @@ -156,9 +153,6 @@ npm exec --package=foo -c '<cmd> [args...]' alias: x </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>This command allows you to run an arbitrary command from an npm package (either one installed locally, or fetched remotely), in a similar context @@ -228,17 +222,12 @@ thus be equivalent to the <code>npx</code> command above:</p> <pre><code>$ npm exec -- foo@latest bar --package=@npmcli/foo </code></pre> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="package"><code>package</code></h4> <ul> <li>Default:</li> <li>Type: String (can be set multiple times)</li> </ul> <p>The package or packages to install for <a href="../commands/npm-exec.html"><code>npm exec</code></a></p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="call"><code>call</code></h4> <ul> <li>Default: ""</li> @@ -248,8 +237,6 @@ thus be equivalent to the <code>npx</code> command above:</p> custom command to be run along with the installed packages.</p> <pre lang="bash"><code>npm exec --package yo --package generator-node --call "yo node" </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -269,8 +256,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -287,8 +272,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -299,9 +282,6 @@ other things (test, exec, publish, etc.) will operate on the root project, all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="examples">Examples</h3> <p>Run the version of <code>tap</code> in the local dependencies, with the provided arguments:</p> diff --git a/deps/npm/docs/output/commands/npm-explain.html b/deps/npm/docs/output/commands/npm-explain.html index 612e18676b4..b7594d426b4 100644 --- a/deps/npm/docs/output/commands/npm-explain.html +++ b/deps/npm/docs/output/commands/npm-explain.html @@ -146,16 +146,10 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm explain <package-spec> alias: why </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>This command will print the chain of dependencies causing a given package to be installed in the current project.</p> @@ -189,9 +183,6 @@ node_modules/nyc/node_modules/find-up dev tap@"^14.10.8" from the root project </code></pre> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="json"><code>json</code></h4> <ul> <li>Default: false</li> @@ -203,8 +194,6 @@ node_modules/nyc/node_modules/find-up saving them to your <code>package.json</code>.</li> </ul> <p>Not supported by all npm commands.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -224,9 +213,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../using-npm/package-spec.html">package spec</a></li> diff --git a/deps/npm/docs/output/commands/npm-explore.html b/deps/npm/docs/output/commands/npm-explore.html index 833605d5e09..f5cd452e8e5 100644 --- a/deps/npm/docs/output/commands/npm-explore.html +++ b/deps/npm/docs/output/commands/npm-explore.html @@ -146,14 +146,8 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm explore <pkg> [ -- <command>] </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>Note: This command is unaware of workspaces.</p> <h3 id="description">Description</h3> <p>Spawn a subshell in the directory of the installed package specified.</p> @@ -166,9 +160,6 @@ immediately terminates.</p> <p>Note that the package is <em>not</em> automatically rebuilt afterwards, so be sure to use <code>npm rebuild <pkg></code> if you make any changes.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="shell"><code>shell</code></h4> <ul> <li>Default: SHELL environment variable, or "bash" on Posix, or "cmd.exe" on @@ -176,9 +167,6 @@ Windows</li> <li>Type: String</li> </ul> <p>The shell to run for the <code>npm explore</code> command.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../configuring-npm/folders.html">npm folders</a></li> diff --git a/deps/npm/docs/output/commands/npm-find-dupes.html b/deps/npm/docs/output/commands/npm-find-dupes.html index 0e3ee085609..5c4dd3d7a50 100644 --- a/deps/npm/docs/output/commands/npm-find-dupes.html +++ b/deps/npm/docs/output/commands/npm-find-dupes.html @@ -146,21 +146,12 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm find-dupes </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>Runs <code>npm dedupe</code> in <code>--dry-run</code> mode, making npm only output the duplications, without actually changing the package tree.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="global-style"><code>global-style</code></h4> <ul> <li>Default: false</li> @@ -172,8 +163,6 @@ direct dependencies will show in <code>node_modules</code> and everything they d on will be flattened in their <code>node_modules</code> folders. This obviously will eliminate some deduping. If used with <code>legacy-bundling</code>, <code>legacy-bundling</code> will be preferred.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="legacy-bundling"><code>legacy-bundling</code></h4> <ul> <li>Default: false</li> @@ -183,8 +172,6 @@ will be preferred.</p> such as the one included with node 0.8, can install the package. This eliminates all automatic deduping. If used with <code>global-style</code> this option will be preferred.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="strict-peer-deps"><code>strict-peer-deps</code></h4> <ul> <li>Default: false</li> @@ -201,8 +188,6 @@ the range set in their package's <code>peerDependencies</code> object.</p> <p>When such and override is performed, a warning is printed, explaining the conflict and the packages involved. If <code>--strict-peer-deps</code> is set, then this warning is treated as a failure.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="package-lock"><code>package-lock</code></h4> <ul> <li>Default: true</li> @@ -211,8 +196,6 @@ this warning is treated as a failure.</p> <p>If set to false, then ignore <code>package-lock.json</code> files when installing. This will also prevent <em>writing</em> <code>package-lock.json</code> if <code>save</code> is true.</p> <p>This configuration does not affect <code>npm ci</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="omit"><code>omit</code></h4> <ul> <li>Default: 'dev' if the <code>NODE_ENV</code> environment variable is set to @@ -227,8 +210,6 @@ physically installed on disk.</p> it will be included.</p> <p>If the resulting omit list includes <code>'dev'</code>, then the <code>NODE_ENV</code> environment variable will be set to <code>'production'</code> for all lifecycle scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="ignore-scripts"><code>ignore-scripts</code></h4> <ul> <li>Default: false</li> @@ -239,8 +220,6 @@ variable will be set to <code>'production'</code> for all lifecycle scripts.</p> <code>npm start</code>, <code>npm stop</code>, <code>npm restart</code>, <code>npm test</code>, and <code>npm run-script</code> will still run their intended script if <code>ignore-scripts</code> is set, but they will <em>not</em> run any pre- or post-scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="audit"><code>audit</code></h4> <ul> <li>Default: true</li> @@ -250,8 +229,6 @@ will <em>not</em> run any pre- or post-scripts.</p> default registry and all registries configured for scopes. See the documentation for <a href="../commands/npm-audit.html"><code>npm audit</code></a> for details on what is submitted.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="bin-links"><code>bin-links</code></h4> <ul> <li>Default: true</li> @@ -262,8 +239,6 @@ executables.</p> <p>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.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="fund"><code>fund</code></h4> <ul> <li>Default: true</li> @@ -271,8 +246,6 @@ systems.</p> </ul> <p>When "true" displays the message at the end of each <code>npm install</code> acknowledging the number of dependencies looking for funding. See <a href="../commands/npm-fund.html"><code>npm fund</code></a> for details.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -292,8 +265,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -310,8 +281,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -322,8 +291,6 @@ other things (test, exec, publish, etc.) will operate on the root project, all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="install-links"><code>install-links</code></h4> <ul> <li>Default: false</li> @@ -332,9 +299,6 @@ the specified workspaces, and not on the root project.</p> <p>When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-dedupe.html">npm dedupe</a></li> diff --git a/deps/npm/docs/output/commands/npm-fund.html b/deps/npm/docs/output/commands/npm-fund.html index 08389cb45ba..cd86db8c177 100644 --- a/deps/npm/docs/output/commands/npm-fund.html +++ b/deps/npm/docs/output/commands/npm-fund.html @@ -146,14 +146,8 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm fund [<package-spec>] </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>This command retrieves information on how to fund the dependencies of a given project. If no package name is provided, it will list all @@ -193,9 +187,6 @@ test-workspaces-fund@1.0.0 `-- foo@2.0.0 </code></pre> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="json"><code>json</code></h4> <ul> <li>Default: false</li> @@ -207,8 +198,6 @@ test-workspaces-fund@1.0.0 saving them to your <code>package.json</code>.</li> </ul> <p>Not supported by all npm commands.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="browser"><code>browser</code></h4> <ul> <li>Default: OS X: <code>"open"</code>, Windows: <code>"start"</code>, Others: <code>"xdg-open"</code></li> @@ -218,8 +207,6 @@ saving them to your <code>package.json</code>.</li> <p>Set to <code>false</code> to suppress browser behavior and instead print urls to terminal.</p> <p>Set to <code>true</code> to use default system URL opener.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="unicode"><code>unicode</code></h4> <ul> <li>Default: false on windows, true on mac/unix systems with a unicode locale, @@ -228,8 +215,6 @@ as defined by the <code>LC_ALL</code>, <code>LC_CTYPE</code>, or <code>LANG</cod </ul> <p>When set to true, npm uses unicode characters in the tree output. When false, it uses ascii characters instead of unicode glyphs.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -249,17 +234,12 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="which"><code>which</code></h4> <ul> <li>Default: null</li> <li>Type: null or Number</li> </ul> <p>If there are multiple funding sources, which 1-indexed source URL to open.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h2 id="see-also">See Also</h2> <ul> <li><a href="../using-npm/package-spec.html">package spec</a></li> diff --git a/deps/npm/docs/output/commands/npm-help-search.html b/deps/npm/docs/output/commands/npm-help-search.html index f99095a05a5..40b07a29b31 100644 --- a/deps/npm/docs/output/commands/npm-help-search.html +++ b/deps/npm/docs/output/commands/npm-help-search.html @@ -146,14 +146,8 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm help-search <text> </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>Note: This command is unaware of workspaces.</p> <h3 id="description">Description</h3> <p>This command will search the npm markdown documentation files for the terms @@ -163,18 +157,12 @@ provided, and then list the results, sorted by relevance.</p> <code>help-search</code>. It is rarely if ever necessary to call this command directly.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="long"><code>long</code></h4> <ul> <li>Default: false</li> <li>Type: Boolean</li> </ul> <p>Show extended information in <code>ls</code>, <code>search</code>, and <code>help-search</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm.html">npm</a></li> diff --git a/deps/npm/docs/output/commands/npm-help.html b/deps/npm/docs/output/commands/npm-help.html index 2e80805fb37..36a8271d457 100644 --- a/deps/npm/docs/output/commands/npm-help.html +++ b/deps/npm/docs/output/commands/npm-help.html @@ -146,16 +146,10 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm help <term> [<terms..>] alias: hlep </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>Note: This command is unaware of workspaces.</p> <h3 id="description">Description</h3> <p>If supplied a topic, then show the appropriate documentation page.</p> @@ -164,9 +158,6 @@ will run the <code>help-search</code> command to find a match. Note that, if <code>help-search</code> finds a single subject, then it will run <code>help</code> on that topic, so unique matches are equivalent to specifying a topic name.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="viewer"><code>viewer</code></h4> <ul> <li>Default: "man" on Posix, "browser" on Windows</li> @@ -174,9 +165,6 @@ topic, so unique matches are equivalent to specifying a topic name.</p> </ul> <p>The program to use to view help content.</p> <p>Set to <code>"browser"</code> to view html help content in the default web browser.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm.html">npm</a></li> diff --git a/deps/npm/docs/output/commands/npm-hook.html b/deps/npm/docs/output/commands/npm-hook.html index 64bf21876db..9a52b484232 100644 --- a/deps/npm/docs/output/commands/npm-hook.html +++ b/deps/npm/docs/output/commands/npm-hook.html @@ -146,17 +146,11 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm hook add <pkg> <url> <secret> [--type=<type>] npm hook ls [pkg] npm hook rm <id> npm hook update <id> <url> <secret> </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>Note: This command is unaware of workspaces.</p> <h3 id="description">Description</h3> <p>Allows you to manage <a href="https://blog.npmjs.org/post/145260155635/introducing-hooks-get-notifications-of-npm">npm @@ -197,17 +191,12 @@ the request came from your own configured hook.</p> <pre lang="bash"><code>$ npm hook rm id-deadbeef </code></pre> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="registry"><code>registry</code></h4> <ul> <li>Default: "<a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a>"</li> <li>Type: URL</li> </ul> <p>The base URL of the npm registry.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="otp"><code>otp</code></h4> <ul> <li>Default: null</li> @@ -217,9 +206,6 @@ the request came from your own configured hook.</p> when publishing or changing package permissions with <code>npm access</code>.</p> <p>If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="https://blog.npmjs.org/post/145260155635/introducing-hooks-get-notifications-of-npm">"Introducing Hooks" blog post</a></li> diff --git a/deps/npm/docs/output/commands/npm-init.html b/deps/npm/docs/output/commands/npm-init.html index 3897be30c76..30e227d026d 100644 --- a/deps/npm/docs/output/commands/npm-init.html +++ b/deps/npm/docs/output/commands/npm-init.html @@ -146,17 +146,11 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm init <package-spec> (same as `npx <package-spec>) npm init <@scope> (same as `npx <@scope>/create`) aliases: create, innit </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p><code>npm init <initializer></code> can be used to set up a new or existing npm package.</p> @@ -262,9 +256,6 @@ dot to represent the current directory in that context, e.g: <code>react-app .</ `-- ... </code></pre> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="yes"><code>yes</code></h4> <ul> <li>Default: null</li> @@ -272,8 +263,6 @@ dot to represent the current directory in that context, e.g: <code>react-app .</ </ul> <p>Automatically answer "yes" to any prompts that npm might print on the command line.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="force"><code>force</code></h4> <ul> <li>Default: false</li> @@ -299,8 +288,6 @@ range (including SemVer-major changes).</li> </ul> <p>If you don't have a clear idea of what you want to do, it is strongly recommended that you do not use this option!</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="scope"><code>scope</code></h4> <ul> <li>Default: the scope of the current project, if any, or ""</li> @@ -322,8 +309,6 @@ installation of packages specified according to the pattern # instead of just named "whatever" npm init --scope=@foo --yes </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -343,8 +328,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -361,8 +344,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces-update"><code>workspaces-update</code></h4> <ul> <li>Default: true</li> @@ -370,8 +351,6 @@ other things (test, exec, publish, etc.) will operate on the root project, </ul> <p>If set to true, the npm cli will run an update after operations that may possibly change the workspaces installed to the <code>node_modules</code> folder.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -382,9 +361,6 @@ possibly change the workspaces installed to the <code>node_modules</code> folder all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../using-npm/package-spec.html">package spec</a></li> diff --git a/deps/npm/docs/output/commands/npm-install-ci-test.html b/deps/npm/docs/output/commands/npm-install-ci-test.html index f7d6e04649c..aec733b43af 100644 --- a/deps/npm/docs/output/commands/npm-install-ci-test.html +++ b/deps/npm/docs/output/commands/npm-install-ci-test.html @@ -146,22 +146,13 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm install-ci-test alias: cit </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>This command runs <code>npm ci</code> followed immediately by <code>npm test</code>.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="save"><code>save</code></h4> <ul> <li>Default: <code>true</code> unless when using <code>npm update</code> where it defaults to <code>false</code></li> @@ -171,8 +162,6 @@ alias: cit <p>When used with the <code>npm rm</code> command, removes the dependency from <code>package.json</code>.</p> <p>Will also prevent writing to <code>package-lock.json</code> if set to <code>false</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="save-exact"><code>save-exact</code></h4> <ul> <li>Default: false</li> @@ -180,8 +169,6 @@ alias: cit </ul> <p>Dependencies saved to package.json will be configured with an exact version rather than using npm's default semver range operator.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="global"><code>global</code></h4> <ul> <li>Default: false</li> @@ -196,8 +183,6 @@ of the current working directory.</li> <li>bin files are linked to <code>{prefix}/bin</code></li> <li>man pages are linked to <code>{prefix}/share/man</code></li> </ul> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="global-style"><code>global-style</code></h4> <ul> <li>Default: false</li> @@ -209,8 +194,6 @@ direct dependencies will show in <code>node_modules</code> and everything they d on will be flattened in their <code>node_modules</code> folders. This obviously will eliminate some deduping. If used with <code>legacy-bundling</code>, <code>legacy-bundling</code> will be preferred.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="legacy-bundling"><code>legacy-bundling</code></h4> <ul> <li>Default: false</li> @@ -220,8 +203,6 @@ will be preferred.</p> such as the one included with node 0.8, can install the package. This eliminates all automatic deduping. If used with <code>global-style</code> this option will be preferred.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="omit"><code>omit</code></h4> <ul> <li>Default: 'dev' if the <code>NODE_ENV</code> environment variable is set to @@ -236,8 +217,6 @@ physically installed on disk.</p> it will be included.</p> <p>If the resulting omit list includes <code>'dev'</code>, then the <code>NODE_ENV</code> environment variable will be set to <code>'production'</code> for all lifecycle scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="strict-peer-deps"><code>strict-peer-deps</code></h4> <ul> <li>Default: false</li> @@ -254,8 +233,6 @@ the range set in their package's <code>peerDependencies</code> object.</p> <p>When such and override is performed, a warning is printed, explaining the conflict and the packages involved. If <code>--strict-peer-deps</code> is set, then this warning is treated as a failure.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="package-lock"><code>package-lock</code></h4> <ul> <li>Default: true</li> @@ -264,8 +241,6 @@ this warning is treated as a failure.</p> <p>If set to false, then ignore <code>package-lock.json</code> files when installing. This will also prevent <em>writing</em> <code>package-lock.json</code> if <code>save</code> is true.</p> <p>This configuration does not affect <code>npm ci</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="foreground-scripts"><code>foreground-scripts</code></h4> <ul> <li>Default: false</li> @@ -276,8 +251,6 @@ scripts for installed packages in the foreground process, sharing standard input, output, and error with the main npm process.</p> <p>Note that this will generally make installs run slower, and be much noisier, but can be useful for debugging.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="ignore-scripts"><code>ignore-scripts</code></h4> <ul> <li>Default: false</li> @@ -288,8 +261,6 @@ but can be useful for debugging.</p> <code>npm start</code>, <code>npm stop</code>, <code>npm restart</code>, <code>npm test</code>, and <code>npm run-script</code> will still run their intended script if <code>ignore-scripts</code> is set, but they will <em>not</em> run any pre- or post-scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="audit"><code>audit</code></h4> <ul> <li>Default: true</li> @@ -299,8 +270,6 @@ will <em>not</em> run any pre- or post-scripts.</p> default registry and all registries configured for scopes. See the documentation for <a href="../commands/npm-audit.html"><code>npm audit</code></a> for details on what is submitted.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="bin-links"><code>bin-links</code></h4> <ul> <li>Default: true</li> @@ -311,8 +280,6 @@ executables.</p> <p>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.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="fund"><code>fund</code></h4> <ul> <li>Default: true</li> @@ -320,8 +287,6 @@ systems.</p> </ul> <p>When "true" displays the message at the end of each <code>npm install</code> acknowledging the number of dependencies looking for funding. See <a href="../commands/npm-fund.html"><code>npm fund</code></a> for details.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="dry-run"><code>dry-run</code></h4> <ul> <li>Default: false</li> @@ -333,8 +298,6 @@ commands that modify your local installation, eg, <code>install</code>, <code>up <code>dedupe</code>, <code>uninstall</code>, as well as <code>pack</code> and <code>publish</code>.</p> <p>Note: This is NOT honored by other network related commands, eg <code>dist-tags</code>, <code>owner</code>, etc.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -354,8 +317,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -372,8 +333,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -384,8 +343,6 @@ other things (test, exec, publish, etc.) will operate on the root project, all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="install-links"><code>install-links</code></h4> <ul> <li>Default: false</li> @@ -394,9 +351,6 @@ the specified workspaces, and not on the root project.</p> <p>When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-install-test.html">npm install-test</a></li> diff --git a/deps/npm/docs/output/commands/npm-install-test.html b/deps/npm/docs/output/commands/npm-install-test.html index bf2ad29400f..e8c97095d17 100644 --- a/deps/npm/docs/output/commands/npm-install-test.html +++ b/deps/npm/docs/output/commands/npm-install-test.html @@ -146,23 +146,14 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm install-test [<package-spec> ...] alias: it </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>This command runs an <code>npm install</code> followed immediately by an <code>npm test</code>. It takes exactly the same arguments as <code>npm install</code>.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="save"><code>save</code></h4> <ul> <li>Default: <code>true</code> unless when using <code>npm update</code> where it defaults to <code>false</code></li> @@ -172,8 +163,6 @@ takes exactly the same arguments as <code>npm install</code>.</p> <p>When used with the <code>npm rm</code> command, removes the dependency from <code>package.json</code>.</p> <p>Will also prevent writing to <code>package-lock.json</code> if set to <code>false</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="save-exact"><code>save-exact</code></h4> <ul> <li>Default: false</li> @@ -181,8 +170,6 @@ takes exactly the same arguments as <code>npm install</code>.</p> </ul> <p>Dependencies saved to package.json will be configured with an exact version rather than using npm's default semver range operator.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="global"><code>global</code></h4> <ul> <li>Default: false</li> @@ -197,8 +184,6 @@ of the current working directory.</li> <li>bin files are linked to <code>{prefix}/bin</code></li> <li>man pages are linked to <code>{prefix}/share/man</code></li> </ul> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="global-style"><code>global-style</code></h4> <ul> <li>Default: false</li> @@ -210,8 +195,6 @@ direct dependencies will show in <code>node_modules</code> and everything they d on will be flattened in their <code>node_modules</code> folders. This obviously will eliminate some deduping. If used with <code>legacy-bundling</code>, <code>legacy-bundling</code> will be preferred.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="legacy-bundling"><code>legacy-bundling</code></h4> <ul> <li>Default: false</li> @@ -221,8 +204,6 @@ will be preferred.</p> such as the one included with node 0.8, can install the package. This eliminates all automatic deduping. If used with <code>global-style</code> this option will be preferred.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="omit"><code>omit</code></h4> <ul> <li>Default: 'dev' if the <code>NODE_ENV</code> environment variable is set to @@ -237,8 +218,6 @@ physically installed on disk.</p> it will be included.</p> <p>If the resulting omit list includes <code>'dev'</code>, then the <code>NODE_ENV</code> environment variable will be set to <code>'production'</code> for all lifecycle scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="strict-peer-deps"><code>strict-peer-deps</code></h4> <ul> <li>Default: false</li> @@ -255,8 +234,6 @@ the range set in their package's <code>peerDependencies</code> object.</p> <p>When such and override is performed, a warning is printed, explaining the conflict and the packages involved. If <code>--strict-peer-deps</code> is set, then this warning is treated as a failure.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="package-lock"><code>package-lock</code></h4> <ul> <li>Default: true</li> @@ -265,8 +242,6 @@ this warning is treated as a failure.</p> <p>If set to false, then ignore <code>package-lock.json</code> files when installing. This will also prevent <em>writing</em> <code>package-lock.json</code> if <code>save</code> is true.</p> <p>This configuration does not affect <code>npm ci</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="foreground-scripts"><code>foreground-scripts</code></h4> <ul> <li>Default: false</li> @@ -277,8 +252,6 @@ scripts for installed packages in the foreground process, sharing standard input, output, and error with the main npm process.</p> <p>Note that this will generally make installs run slower, and be much noisier, but can be useful for debugging.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="ignore-scripts"><code>ignore-scripts</code></h4> <ul> <li>Default: false</li> @@ -289,8 +262,6 @@ but can be useful for debugging.</p> <code>npm start</code>, <code>npm stop</code>, <code>npm restart</code>, <code>npm test</code>, and <code>npm run-script</code> will still run their intended script if <code>ignore-scripts</code> is set, but they will <em>not</em> run any pre- or post-scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="audit"><code>audit</code></h4> <ul> <li>Default: true</li> @@ -300,8 +271,6 @@ will <em>not</em> run any pre- or post-scripts.</p> default registry and all registries configured for scopes. See the documentation for <a href="../commands/npm-audit.html"><code>npm audit</code></a> for details on what is submitted.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="bin-links"><code>bin-links</code></h4> <ul> <li>Default: true</li> @@ -312,8 +281,6 @@ executables.</p> <p>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.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="fund"><code>fund</code></h4> <ul> <li>Default: true</li> @@ -321,8 +288,6 @@ systems.</p> </ul> <p>When "true" displays the message at the end of each <code>npm install</code> acknowledging the number of dependencies looking for funding. See <a href="../commands/npm-fund.html"><code>npm fund</code></a> for details.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="dry-run"><code>dry-run</code></h4> <ul> <li>Default: false</li> @@ -334,8 +299,6 @@ commands that modify your local installation, eg, <code>install</code>, <code>up <code>dedupe</code>, <code>uninstall</code>, as well as <code>pack</code> and <code>publish</code>.</p> <p>Note: This is NOT honored by other network related commands, eg <code>dist-tags</code>, <code>owner</code>, etc.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -355,8 +318,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -373,8 +334,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -385,8 +344,6 @@ other things (test, exec, publish, etc.) will operate on the root project, all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="install-links"><code>install-links</code></h4> <ul> <li>Default: false</li> @@ -395,9 +352,6 @@ the specified workspaces, and not on the root project.</p> <p>When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-install.html">npm install</a></li> diff --git a/deps/npm/docs/output/commands/npm-install.html b/deps/npm/docs/output/commands/npm-install.html index 7702ab5c167..d8cb253edea 100644 --- a/deps/npm/docs/output/commands/npm-install.html +++ b/deps/npm/docs/output/commands/npm-install.html @@ -146,16 +146,10 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm install [<package-spec> ...] aliases: add, i, in, ins, inst, insta, instal, isnt, isnta, isntal, isntall </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>This command installs a package and any packages that it depends on. If the package has a package-lock, or an npm shrinkwrap file, or a yarn lock file, @@ -486,9 +480,6 @@ even if a local copy exists on disk.</p> params have some effect on installation, since that's most of what npm does.</p> <p>These are some of the most common options related to installation.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="save"><code>save</code></h4> <ul> <li>Default: <code>true</code> unless when using <code>npm update</code> where it defaults to <code>false</code></li> @@ -498,8 +489,6 @@ does.</p> <p>When used with the <code>npm rm</code> command, removes the dependency from <code>package.json</code>.</p> <p>Will also prevent writing to <code>package-lock.json</code> if set to <code>false</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="save-exact"><code>save-exact</code></h4> <ul> <li>Default: false</li> @@ -507,8 +496,6 @@ does.</p> </ul> <p>Dependencies saved to package.json will be configured with an exact version rather than using npm's default semver range operator.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="global"><code>global</code></h4> <ul> <li>Default: false</li> @@ -523,8 +510,6 @@ of the current working directory.</li> <li>bin files are linked to <code>{prefix}/bin</code></li> <li>man pages are linked to <code>{prefix}/share/man</code></li> </ul> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="global-style"><code>global-style</code></h4> <ul> <li>Default: false</li> @@ -536,8 +521,6 @@ direct dependencies will show in <code>node_modules</code> and everything they d on will be flattened in their <code>node_modules</code> folders. This obviously will eliminate some deduping. If used with <code>legacy-bundling</code>, <code>legacy-bundling</code> will be preferred.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="legacy-bundling"><code>legacy-bundling</code></h4> <ul> <li>Default: false</li> @@ -547,8 +530,6 @@ will be preferred.</p> such as the one included with node 0.8, can install the package. This eliminates all automatic deduping. If used with <code>global-style</code> this option will be preferred.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="omit"><code>omit</code></h4> <ul> <li>Default: 'dev' if the <code>NODE_ENV</code> environment variable is set to @@ -563,8 +544,6 @@ physically installed on disk.</p> it will be included.</p> <p>If the resulting omit list includes <code>'dev'</code>, then the <code>NODE_ENV</code> environment variable will be set to <code>'production'</code> for all lifecycle scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="strict-peer-deps"><code>strict-peer-deps</code></h4> <ul> <li>Default: false</li> @@ -581,8 +560,6 @@ the range set in their package's <code>peerDependencies</code> object.</p> <p>When such and override is performed, a warning is printed, explaining the conflict and the packages involved. If <code>--strict-peer-deps</code> is set, then this warning is treated as a failure.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="package-lock"><code>package-lock</code></h4> <ul> <li>Default: true</li> @@ -591,8 +568,6 @@ this warning is treated as a failure.</p> <p>If set to false, then ignore <code>package-lock.json</code> files when installing. This will also prevent <em>writing</em> <code>package-lock.json</code> if <code>save</code> is true.</p> <p>This configuration does not affect <code>npm ci</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="foreground-scripts"><code>foreground-scripts</code></h4> <ul> <li>Default: false</li> @@ -603,8 +578,6 @@ scripts for installed packages in the foreground process, sharing standard input, output, and error with the main npm process.</p> <p>Note that this will generally make installs run slower, and be much noisier, but can be useful for debugging.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="ignore-scripts"><code>ignore-scripts</code></h4> <ul> <li>Default: false</li> @@ -615,8 +588,6 @@ but can be useful for debugging.</p> <code>npm start</code>, <code>npm stop</code>, <code>npm restart</code>, <code>npm test</code>, and <code>npm run-script</code> will still run their intended script if <code>ignore-scripts</code> is set, but they will <em>not</em> run any pre- or post-scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="audit"><code>audit</code></h4> <ul> <li>Default: true</li> @@ -626,8 +597,6 @@ will <em>not</em> run any pre- or post-scripts.</p> default registry and all registries configured for scopes. See the documentation for <a href="../commands/npm-audit.html"><code>npm audit</code></a> for details on what is submitted.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="bin-links"><code>bin-links</code></h4> <ul> <li>Default: true</li> @@ -638,8 +607,6 @@ executables.</p> <p>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.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="fund"><code>fund</code></h4> <ul> <li>Default: true</li> @@ -647,8 +614,6 @@ systems.</p> </ul> <p>When "true" displays the message at the end of each <code>npm install</code> acknowledging the number of dependencies looking for funding. See <a href="../commands/npm-fund.html"><code>npm fund</code></a> for details.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="dry-run"><code>dry-run</code></h4> <ul> <li>Default: false</li> @@ -660,8 +625,6 @@ commands that modify your local installation, eg, <code>install</code>, <code>up <code>dedupe</code>, <code>uninstall</code>, as well as <code>pack</code> and <code>publish</code>.</p> <p>Note: This is NOT honored by other network related commands, eg <code>dist-tags</code>, <code>owner</code>, etc.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -681,8 +644,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -699,8 +660,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -711,8 +670,6 @@ other things (test, exec, publish, etc.) will operate on the root project, all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="install-links"><code>install-links</code></h4> <ul> <li>Default: false</li> @@ -721,9 +678,6 @@ the specified workspaces, and not on the root project.</p> <p>When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="algorithm">Algorithm</h3> <p>Given a <code>package{dep}</code> structure: <code>A{B,C}, B{C}, C{D}</code>, the npm install algorithm produces:</p> diff --git a/deps/npm/docs/output/commands/npm-link.html b/deps/npm/docs/output/commands/npm-link.html index cd31a3ee0df..2ab5384181b 100644 --- a/deps/npm/docs/output/commands/npm-link.html +++ b/deps/npm/docs/output/commands/npm-link.html @@ -146,16 +146,10 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm link [<package-spec>] alias: ln </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>This is handy for installing your own stuff, so that you can work on it and test iteratively without having to continually rebuild.</p> @@ -223,9 +217,6 @@ conflicting dependencies.</p> <p><code>npm link --workspace <name></code> will create a global link to the specified workspace(s).</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="save"><code>save</code></h4> <ul> <li>Default: <code>true</code> unless when using <code>npm update</code> where it defaults to <code>false</code></li> @@ -235,8 +226,6 @@ workspace(s).</p> <p>When used with the <code>npm rm</code> command, removes the dependency from <code>package.json</code>.</p> <p>Will also prevent writing to <code>package-lock.json</code> if set to <code>false</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="save-exact"><code>save-exact</code></h4> <ul> <li>Default: false</li> @@ -244,8 +233,6 @@ workspace(s).</p> </ul> <p>Dependencies saved to package.json will be configured with an exact version rather than using npm's default semver range operator.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="global"><code>global</code></h4> <ul> <li>Default: false</li> @@ -260,8 +247,6 @@ of the current working directory.</li> <li>bin files are linked to <code>{prefix}/bin</code></li> <li>man pages are linked to <code>{prefix}/share/man</code></li> </ul> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="global-style"><code>global-style</code></h4> <ul> <li>Default: false</li> @@ -273,8 +258,6 @@ direct dependencies will show in <code>node_modules</code> and everything they d on will be flattened in their <code>node_modules</code> folders. This obviously will eliminate some deduping. If used with <code>legacy-bundling</code>, <code>legacy-bundling</code> will be preferred.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="legacy-bundling"><code>legacy-bundling</code></h4> <ul> <li>Default: false</li> @@ -284,8 +267,6 @@ will be preferred.</p> such as the one included with node 0.8, can install the package. This eliminates all automatic deduping. If used with <code>global-style</code> this option will be preferred.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="strict-peer-deps"><code>strict-peer-deps</code></h4> <ul> <li>Default: false</li> @@ -302,8 +283,6 @@ the range set in their package's <code>peerDependencies</code> object.</p> <p>When such and override is performed, a warning is printed, explaining the conflict and the packages involved. If <code>--strict-peer-deps</code> is set, then this warning is treated as a failure.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="package-lock"><code>package-lock</code></h4> <ul> <li>Default: true</li> @@ -312,8 +291,6 @@ this warning is treated as a failure.</p> <p>If set to false, then ignore <code>package-lock.json</code> files when installing. This will also prevent <em>writing</em> <code>package-lock.json</code> if <code>save</code> is true.</p> <p>This configuration does not affect <code>npm ci</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="omit"><code>omit</code></h4> <ul> <li>Default: 'dev' if the <code>NODE_ENV</code> environment variable is set to @@ -328,8 +305,6 @@ physically installed on disk.</p> it will be included.</p> <p>If the resulting omit list includes <code>'dev'</code>, then the <code>NODE_ENV</code> environment variable will be set to <code>'production'</code> for all lifecycle scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="ignore-scripts"><code>ignore-scripts</code></h4> <ul> <li>Default: false</li> @@ -340,8 +315,6 @@ variable will be set to <code>'production'</code> for all lifecycle scripts.</p> <code>npm start</code>, <code>npm stop</code>, <code>npm restart</code>, <code>npm test</code>, and <code>npm run-script</code> will still run their intended script if <code>ignore-scripts</code> is set, but they will <em>not</em> run any pre- or post-scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="audit"><code>audit</code></h4> <ul> <li>Default: true</li> @@ -351,8 +324,6 @@ will <em>not</em> run any pre- or post-scripts.</p> default registry and all registries configured for scopes. See the documentation for <a href="../commands/npm-audit.html"><code>npm audit</code></a> for details on what is submitted.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="bin-links"><code>bin-links</code></h4> <ul> <li>Default: true</li> @@ -363,8 +334,6 @@ executables.</p> <p>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.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="fund"><code>fund</code></h4> <ul> <li>Default: true</li> @@ -372,8 +341,6 @@ systems.</p> </ul> <p>When "true" displays the message at the end of each <code>npm install</code> acknowledging the number of dependencies looking for funding. See <a href="../commands/npm-fund.html"><code>npm fund</code></a> for details.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="dry-run"><code>dry-run</code></h4> <ul> <li>Default: false</li> @@ -385,8 +352,6 @@ commands that modify your local installation, eg, <code>install</code>, <code>up <code>dedupe</code>, <code>uninstall</code>, as well as <code>pack</code> and <code>publish</code>.</p> <p>Note: This is NOT honored by other network related commands, eg <code>dist-tags</code>, <code>owner</code>, etc.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -406,8 +371,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -424,8 +387,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -436,8 +397,6 @@ other things (test, exec, publish, etc.) will operate on the root project, all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="install-links"><code>install-links</code></h4> <ul> <li>Default: false</li> @@ -446,9 +405,6 @@ the specified workspaces, and not on the root project.</p> <p>When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../using-npm/package-spec.html">package spec</a></li> diff --git a/deps/npm/docs/output/commands/npm-logout.html b/deps/npm/docs/output/commands/npm-logout.html index 112065a63dd..6449df311c4 100644 --- a/deps/npm/docs/output/commands/npm-logout.html +++ b/deps/npm/docs/output/commands/npm-logout.html @@ -146,14 +146,8 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm logout </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>Note: This command is unaware of workspaces.</p> <h3 id="description">Description</h3> <p>When logged into a registry that supports token-based authentication, tell @@ -165,17 +159,12 @@ In this case, it will <em>only</em> affect the current environment.</p> <p>If <code>--scope</code> is provided, this will find the credentials for the registry connected to that scope, if set.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="registry"><code>registry</code></h4> <ul> <li>Default: "<a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a>"</li> <li>Type: URL</li> </ul> <p>The base URL of the npm registry.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="scope"><code>scope</code></h4> <ul> <li>Default: the scope of the current project, if any, or ""</li> @@ -197,9 +186,6 @@ installation of packages specified according to the pattern # instead of just named "whatever" npm init --scope=@foo --yes </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-adduser.html">npm adduser</a></li> diff --git a/deps/npm/docs/output/commands/npm-ls.html b/deps/npm/docs/output/commands/npm-ls.html index 3733fe5747c..4abe5cd01d7 100644 --- a/deps/npm/docs/output/commands/npm-ls.html +++ b/deps/npm/docs/output/commands/npm-ls.html @@ -146,16 +146,10 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm ls <package-spec> alias: list </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>This command will print to stdout all the versions of packages that are installed, as well as their dependencies when <code>--all</code> is specified, in a @@ -166,7 +160,7 @@ tree at all, use <a href="../commands/npm-explain.html"><code>npm explain</code> the results to only the paths to the packages named. Note that nested packages will <em>also</em> show the paths to the specified packages. For example, running <code>npm ls promzard</code> in npm's source tree will show:</p> -<pre lang="bash"><code>npm@8.19.2 /path/to/npm +<pre lang="bash"><code>npm@8.19.3 /path/to/npm └─┬ init-package-json@0.0.4 └── promzard@0.1.5 </code></pre> @@ -199,9 +193,6 @@ provided.</p> of this command, is currently underway. Expect significant changes to at least the default human-readable <code>npm ls</code> output in npm v8.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="all"><code>all</code></h4> <ul> <li>Default: false</li> @@ -210,8 +201,6 @@ least the default human-readable <code>npm ls</code> output in npm v8.</p> <p>When running <code>npm outdated</code> and <code>npm ls</code>, setting <code>--all</code> will show all outdated or installed packages, rather than only those directly depended upon by the current project.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="json"><code>json</code></h4> <ul> <li>Default: false</li> @@ -223,16 +212,12 @@ upon by the current project.</p> saving them to your <code>package.json</code>.</li> </ul> <p>Not supported by all npm commands.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="long"><code>long</code></h4> <ul> <li>Default: false</li> <li>Type: Boolean</li> </ul> <p>Show extended information in <code>ls</code>, <code>search</code>, and <code>help-search</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="parseable"><code>parseable</code></h4> <ul> <li>Default: false</li> @@ -240,8 +225,6 @@ saving them to your <code>package.json</code>.</li> </ul> <p>Output parseable results from commands that write to standard output. For <code>npm search</code>, this will be tab-separated table format.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="global"><code>global</code></h4> <ul> <li>Default: false</li> @@ -256,8 +239,6 @@ of the current working directory.</li> <li>bin files are linked to <code>{prefix}/bin</code></li> <li>man pages are linked to <code>{prefix}/share/man</code></li> </ul> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="depth"><code>depth</code></h4> <ul> <li>Default: <code>Infinity</code> if <code>--all</code> is set, otherwise <code>1</code></li> @@ -266,8 +247,6 @@ of the current working directory.</li> <p>The depth to go when recursing packages for <code>npm ls</code>.</p> <p>If not set, <code>npm ls</code> will show only the immediate dependencies of the root project. If <code>--all</code> is set, then npm will show all dependencies by default.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="omit"><code>omit</code></h4> <ul> <li>Default: 'dev' if the <code>NODE_ENV</code> environment variable is set to @@ -282,16 +261,12 @@ physically installed on disk.</p> it will be included.</p> <p>If the resulting omit list includes <code>'dev'</code>, then the <code>NODE_ENV</code> environment variable will be set to <code>'production'</code> for all lifecycle scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="link"><code>link</code></h4> <ul> <li>Default: false</li> <li>Type: Boolean</li> </ul> <p>Used with <code>npm ls</code>, limiting output to only those packages that are linked.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="package-lock-only"><code>package-lock-only</code></h4> <ul> <li>Default: false</li> @@ -303,8 +278,6 @@ ignoring <code>node_modules</code>.</p> instead of checking <code>node_modules</code> and downloading dependencies.</p> <p>For <code>list</code> this means the output will be based on the tree described by the <code>package-lock.json</code>, rather than the contents of <code>node_modules</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="unicode"><code>unicode</code></h4> <ul> <li>Default: false on windows, true on mac/unix systems with a unicode locale, @@ -313,8 +286,6 @@ as defined by the <code>LC_ALL</code>, <code>LC_CTYPE</code>, or <code>LANG</cod </ul> <p>When set to true, npm uses unicode characters in the tree output. When false, it uses ascii characters instead of unicode glyphs.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -334,8 +305,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -352,8 +321,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -364,8 +331,6 @@ other things (test, exec, publish, etc.) will operate on the root project, all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="install-links"><code>install-links</code></h4> <ul> <li>Default: false</li> @@ -374,9 +339,6 @@ the specified workspaces, and not on the root project.</p> <p>When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../using-npm/package-spec.html">package spec</a></li> diff --git a/deps/npm/docs/output/commands/npm-org.html b/deps/npm/docs/output/commands/npm-org.html index a8aee32fb74..e190a437cd1 100644 --- a/deps/npm/docs/output/commands/npm-org.html +++ b/deps/npm/docs/output/commands/npm-org.html @@ -146,18 +146,12 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm org set orgname username [developer | admin | owner] npm org rm orgname username npm org ls orgname [<username>] alias: ogr </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>Note: This command is unaware of workspaces.</p> <h3 id="example">Example</h3> <p>Add a new developer to an org:</p> @@ -183,17 +177,12 @@ alias: ogr organization. It supports adding and removing users, changing their roles, listing them, and finding specific ones and their roles.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="registry"><code>registry</code></h4> <ul> <li>Default: "<a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a>"</li> <li>Type: URL</li> </ul> <p>The base URL of the npm registry.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="otp"><code>otp</code></h4> <ul> <li>Default: null</li> @@ -203,8 +192,6 @@ listing them, and finding specific ones and their roles.</p> when publishing or changing package permissions with <code>npm access</code>.</p> <p>If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="json"><code>json</code></h4> <ul> <li>Default: false</li> @@ -216,8 +203,6 @@ password, npm will prompt on the command line for one.</p> saving them to your <code>package.json</code>.</li> </ul> <p>Not supported by all npm commands.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="parseable"><code>parseable</code></h4> <ul> <li>Default: false</li> @@ -225,9 +210,6 @@ saving them to your <code>package.json</code>.</li> </ul> <p>Output parseable results from commands that write to standard output. For <code>npm search</code>, this will be tab-separated table format.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../using-npm/orgs.html">using orgs</a></li> diff --git a/deps/npm/docs/output/commands/npm-outdated.html b/deps/npm/docs/output/commands/npm-outdated.html index 57740228c48..f22ef60aef9 100644 --- a/deps/npm/docs/output/commands/npm-outdated.html +++ b/deps/npm/docs/output/commands/npm-outdated.html @@ -146,14 +146,8 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm outdated [<package-spec> ...] </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>This command will check the registry to see if any (or, specific) installed packages are currently outdated.</p> @@ -221,9 +215,6 @@ npm uses dist-tags to manage its <code>latest</code> and <code>next</code> relea scratch or running <code>npm update</code> will bring it up to spec.</li> </ul> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="all"><code>all</code></h4> <ul> <li>Default: false</li> @@ -232,8 +223,6 @@ scratch or running <code>npm update</code> will bring it up to spec.</li> <p>When running <code>npm outdated</code> and <code>npm ls</code>, setting <code>--all</code> will show all outdated or installed packages, rather than only those directly depended upon by the current project.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="json"><code>json</code></h4> <ul> <li>Default: false</li> @@ -245,16 +234,12 @@ upon by the current project.</p> saving them to your <code>package.json</code>.</li> </ul> <p>Not supported by all npm commands.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="long"><code>long</code></h4> <ul> <li>Default: false</li> <li>Type: Boolean</li> </ul> <p>Show extended information in <code>ls</code>, <code>search</code>, and <code>help-search</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="parseable"><code>parseable</code></h4> <ul> <li>Default: false</li> @@ -262,8 +247,6 @@ saving them to your <code>package.json</code>.</li> </ul> <p>Output parseable results from commands that write to standard output. For <code>npm search</code>, this will be tab-separated table format.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="global"><code>global</code></h4> <ul> <li>Default: false</li> @@ -278,8 +261,6 @@ of the current working directory.</li> <li>bin files are linked to <code>{prefix}/bin</code></li> <li>man pages are linked to <code>{prefix}/share/man</code></li> </ul> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -299,9 +280,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../using-npm/package-spec.html">package spec</a></li> diff --git a/deps/npm/docs/output/commands/npm-owner.html b/deps/npm/docs/output/commands/npm-owner.html index bf47a0ce04f..fd7f8a843ac 100644 --- a/deps/npm/docs/output/commands/npm-owner.html +++ b/deps/npm/docs/output/commands/npm-owner.html @@ -146,18 +146,12 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm owner add <user> <package-spec> npm owner rm <user> <package-spec> npm owner ls <package-spec> alias: author </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>Note: This command is unaware of workspaces.</p> <h3 id="description">Description</h3> <p>Manage ownership of published packages.</p> @@ -176,17 +170,12 @@ that is not implemented at this time.</p> <a href="../commands/npm-profile.html"><code>npm-profile</code></a>) then you'll need to include an otp on the command line when changing ownership with <code>--otp</code>.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="registry"><code>registry</code></h4> <ul> <li>Default: "<a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a>"</li> <li>Type: URL</li> </ul> <p>The base URL of the npm registry.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="otp"><code>otp</code></h4> <ul> <li>Default: null</li> @@ -196,8 +185,6 @@ on the command line when changing ownership with <code>--otp</code>.</p> when publishing or changing package permissions with <code>npm access</code>.</p> <p>If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -217,8 +204,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -235,9 +220,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../using-npm/package-spec.html">package spec</a></li> diff --git a/deps/npm/docs/output/commands/npm-pack.html b/deps/npm/docs/output/commands/npm-pack.html index 387becd8c1f..2abe8dd6097 100644 --- a/deps/npm/docs/output/commands/npm-pack.html +++ b/deps/npm/docs/output/commands/npm-pack.html @@ -146,18 +146,9 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm pack <package-spec> </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="dry-run"><code>dry-run</code></h4> <ul> <li>Default: false</li> @@ -169,8 +160,6 @@ commands that modify your local installation, eg, <code>install</code>, <code>up <code>dedupe</code>, <code>uninstall</code>, as well as <code>pack</code> and <code>publish</code>.</p> <p>Note: This is NOT honored by other network related commands, eg <code>dist-tags</code>, <code>owner</code>, etc.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="json"><code>json</code></h4> <ul> <li>Default: false</li> @@ -182,16 +171,12 @@ commands that modify your local installation, eg, <code>install</code>, <code>up saving them to your <code>package.json</code>.</li> </ul> <p>Not supported by all npm commands.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="pack-destination"><code>pack-destination</code></h4> <ul> <li>Default: "."</li> <li>Type: String</li> </ul> <p>Directory in which <code>npm pack</code> will save tarballs.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -211,8 +196,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -229,8 +212,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -241,9 +222,6 @@ other things (test, exec, publish, etc.) will operate on the root project, all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>For anything that's installable (that is, a package folder, tarball, tarball url, git url, name@tag, name@version, name, or scoped name), this diff --git a/deps/npm/docs/output/commands/npm-ping.html b/deps/npm/docs/output/commands/npm-ping.html index 529b7931ef9..c8367e56cd6 100644 --- a/deps/npm/docs/output/commands/npm-ping.html +++ b/deps/npm/docs/output/commands/npm-ping.html @@ -146,14 +146,8 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm ping </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>Note: This command is unaware of workspaces.</p> <h3 id="description">Description</h3> <p>Ping the configured or given npm registry and verify authentication. @@ -167,18 +161,12 @@ npm ERR! code E404 npm ERR! 404 Not Found - GET http://www.foo.com/-/ping?write=true </code></pre> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="registry"><code>registry</code></h4> <ul> <li>Default: "<a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a>"</li> <li>Type: URL</li> </ul> <p>The base URL of the npm registry.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-doctor.html">npm doctor</a></li> diff --git a/deps/npm/docs/output/commands/npm-pkg.html b/deps/npm/docs/output/commands/npm-pkg.html index 95635ee6028..e612b5516e1 100644 --- a/deps/npm/docs/output/commands/npm-pkg.html +++ b/deps/npm/docs/output/commands/npm-pkg.html @@ -146,18 +146,12 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm pkg set <key>=<value> [<key>=<value> ...] npm pkg get [<key> [<key> ...]] npm pkg delete <key> [<key> ...] npm pkg set [<array>[<index>].<key>=<value> ...] npm pkg set [<array>[].<key>=<value> ...] </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>A command that automates the management of <code>package.json</code> files. <code>npm pkg</code> provide 3 different sub commands that allow you to modify or retrieve @@ -267,9 +261,6 @@ returned from each of the configured workspaces, e.g:</p> } </code></pre> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="force"><code>force</code></h4> <ul> <li>Default: false</li> @@ -295,8 +286,6 @@ range (including SemVer-major changes).</li> </ul> <p>If you don't have a clear idea of what you want to do, it is strongly recommended that you do not use this option!</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="json"><code>json</code></h4> <ul> <li>Default: false</li> @@ -308,8 +297,6 @@ recommended that you do not use this option!</p> saving them to your <code>package.json</code>.</li> </ul> <p>Not supported by all npm commands.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -329,8 +316,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -347,9 +332,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h2 id="see-also">See Also</h2> <ul> <li><a href="../commands/npm-install.html">npm install</a></li> diff --git a/deps/npm/docs/output/commands/npm-prefix.html b/deps/npm/docs/output/commands/npm-prefix.html index 2f302144269..00201507b89 100644 --- a/deps/npm/docs/output/commands/npm-prefix.html +++ b/deps/npm/docs/output/commands/npm-prefix.html @@ -146,14 +146,8 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm prefix [-g] </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>Note: This command is unaware of workspaces.</p> <h3 id="description">Description</h3> <p>Print the local prefix to standard output. This is the closest parent directory @@ -169,9 +163,6 @@ also specified.</p> /usr/local </code></pre> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="global"><code>global</code></h4> <ul> <li>Default: false</li> @@ -186,9 +177,6 @@ of the current working directory.</li> <li>bin files are linked to <code>{prefix}/bin</code></li> <li>man pages are linked to <code>{prefix}/share/man</code></li> </ul> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-root.html">npm root</a></li> diff --git a/deps/npm/docs/output/commands/npm-profile.html b/deps/npm/docs/output/commands/npm-profile.html index 89ca083b122..14d0c0c3051 100644 --- a/deps/npm/docs/output/commands/npm-profile.html +++ b/deps/npm/docs/output/commands/npm-profile.html @@ -146,17 +146,11 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm profile enable-2fa [auth-only|auth-and-writes] npm profile disable-2fa npm profile get [<key>] npm profile set <key> <value> </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>Note: This command is unaware of workspaces.</p> <h3 id="description">Description</h3> <p>Change your profile information on the registry. Note that this command @@ -219,17 +213,12 @@ dist-tag, or changing access via <code>npm access</code> and <code>npm owner</co <h3 id="details">Details</h3> <p>Some of these commands may not be available on non npmjs.com registries.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="registry"><code>registry</code></h4> <ul> <li>Default: "<a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a>"</li> <li>Type: URL</li> </ul> <p>The base URL of the npm registry.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="json"><code>json</code></h4> <ul> <li>Default: false</li> @@ -241,8 +230,6 @@ dist-tag, or changing access via <code>npm access</code> and <code>npm owner</co saving them to your <code>package.json</code>.</li> </ul> <p>Not supported by all npm commands.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="parseable"><code>parseable</code></h4> <ul> <li>Default: false</li> @@ -250,8 +237,6 @@ saving them to your <code>package.json</code>.</li> </ul> <p>Output parseable results from commands that write to standard output. For <code>npm search</code>, this will be tab-separated table format.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="otp"><code>otp</code></h4> <ul> <li>Default: null</li> @@ -261,9 +246,6 @@ saving them to your <code>package.json</code>.</li> when publishing or changing package permissions with <code>npm access</code>.</p> <p>If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-adduser.html">npm adduser</a></li> diff --git a/deps/npm/docs/output/commands/npm-prune.html b/deps/npm/docs/output/commands/npm-prune.html index 0a248629bd8..c276624adbf 100644 --- a/deps/npm/docs/output/commands/npm-prune.html +++ b/deps/npm/docs/output/commands/npm-prune.html @@ -146,14 +146,8 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm prune [[<@scope>/]<pkg>...] </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>This command removes "extraneous" packages. If a package name is provided, then only packages matching one of the supplied names are removed.</p> @@ -171,9 +165,6 @@ only need this command with the <code>--production</code> flag. However, in the world, operation is not always "normal". When crashes or mistakes happen, this command can help clean up any resulting garbage.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="omit"><code>omit</code></h4> <ul> <li>Default: 'dev' if the <code>NODE_ENV</code> environment variable is set to @@ -188,8 +179,6 @@ physically installed on disk.</p> it will be included.</p> <p>If the resulting omit list includes <code>'dev'</code>, then the <code>NODE_ENV</code> environment variable will be set to <code>'production'</code> for all lifecycle scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="dry-run"><code>dry-run</code></h4> <ul> <li>Default: false</li> @@ -201,8 +190,6 @@ commands that modify your local installation, eg, <code>install</code>, <code>up <code>dedupe</code>, <code>uninstall</code>, as well as <code>pack</code> and <code>publish</code>.</p> <p>Note: This is NOT honored by other network related commands, eg <code>dist-tags</code>, <code>owner</code>, etc.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="json"><code>json</code></h4> <ul> <li>Default: false</li> @@ -214,8 +201,6 @@ commands that modify your local installation, eg, <code>install</code>, <code>up saving them to your <code>package.json</code>.</li> </ul> <p>Not supported by all npm commands.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="foreground-scripts"><code>foreground-scripts</code></h4> <ul> <li>Default: false</li> @@ -226,8 +211,6 @@ scripts for installed packages in the foreground process, sharing standard input, output, and error with the main npm process.</p> <p>Note that this will generally make installs run slower, and be much noisier, but can be useful for debugging.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="ignore-scripts"><code>ignore-scripts</code></h4> <ul> <li>Default: false</li> @@ -238,8 +221,6 @@ but can be useful for debugging.</p> <code>npm start</code>, <code>npm stop</code>, <code>npm restart</code>, <code>npm test</code>, and <code>npm run-script</code> will still run their intended script if <code>ignore-scripts</code> is set, but they will <em>not</em> run any pre- or post-scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -259,8 +240,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -277,8 +256,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -289,8 +266,6 @@ other things (test, exec, publish, etc.) will operate on the root project, all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="install-links"><code>install-links</code></h4> <ul> <li>Default: false</li> @@ -299,9 +274,6 @@ the specified workspaces, and not on the root project.</p> <p>When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-uninstall.html">npm uninstall</a></li> diff --git a/deps/npm/docs/output/commands/npm-publish.html b/deps/npm/docs/output/commands/npm-publish.html index 019295ab1f0..66b6f12b062 100644 --- a/deps/npm/docs/output/commands/npm-publish.html +++ b/deps/npm/docs/output/commands/npm-publish.html @@ -146,14 +146,8 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm publish <package-spec> </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>Publishes a package to the registry so that it can be installed by name.</p> <p>By default npm will publish to the public registry. This can be @@ -224,9 +218,6 @@ un-ignored with a <code>!</code> rule in a <code>.npmignore</code> or <code>.git included in the published package, as well as details on how the package is built.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="tag"><code>tag</code></h4> <ul> <li>Default: "latest"</li> @@ -238,8 +229,6 @@ then it will install the specified tag.</p> command, if no explicit tag is given.</p> <p>When used by the <code>npm diff</code> command, this is the tag used to fetch the tarball that will be compared with the local files by default.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="access"><code>access</code></h4> <ul> <li>Default: 'restricted' for scoped packages, 'public' for unscoped packages</li> @@ -254,8 +243,6 @@ the package access level on the initial publish of the package. Any subsequent <code>npm publish</code> commands using the <code>--access</code> flag will not have an effect to the access level. To make changes to the access level after the initial publish use <code>npm access</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="dry-run"><code>dry-run</code></h4> <ul> <li>Default: false</li> @@ -267,8 +254,6 @@ commands that modify your local installation, eg, <code>install</code>, <code>up <code>dedupe</code>, <code>uninstall</code>, as well as <code>pack</code> and <code>publish</code>.</p> <p>Note: This is NOT honored by other network related commands, eg <code>dist-tags</code>, <code>owner</code>, etc.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="otp"><code>otp</code></h4> <ul> <li>Default: null</li> @@ -278,8 +263,6 @@ commands that modify your local installation, eg, <code>install</code>, <code>up when publishing or changing package permissions with <code>npm access</code>.</p> <p>If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -299,8 +282,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -317,8 +298,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -329,9 +308,6 @@ other things (test, exec, publish, etc.) will operate on the root project, all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../using-npm/package-spec.html">package spec</a></li> diff --git a/deps/npm/docs/output/commands/npm-query.html b/deps/npm/docs/output/commands/npm-query.html index d567d2b8731..72ea62db4f8 100644 --- a/deps/npm/docs/output/commands/npm-query.html +++ b/deps/npm/docs/output/commands/npm-query.html @@ -146,14 +146,8 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm query <selector> </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>The <code>npm query</code> command allows for usage of css selectors in order to retrieve an array of dependency objects.</p> @@ -271,9 +265,6 @@ npm query ":type(git)" | jq 'map(.name)' | xargs -I {} npm why {} ... </code></pre> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="global"><code>global</code></h4> <ul> <li>Default: false</li> @@ -288,8 +279,6 @@ of the current working directory.</li> <li>bin files are linked to <code>{prefix}/bin</code></li> <li>man pages are linked to <code>{prefix}/share/man</code></li> </ul> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -309,8 +298,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -327,8 +314,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -339,9 +324,6 @@ other things (test, exec, publish, etc.) will operate on the root project, all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h2 id="see-also">See Also</h2> <ul> <li><a href="../using-npm/dependency-selectors.html">dependency selectors</a></li> diff --git a/deps/npm/docs/output/commands/npm-rebuild.html b/deps/npm/docs/output/commands/npm-rebuild.html index 2fdd821d592..49c527b27ef 100644 --- a/deps/npm/docs/output/commands/npm-rebuild.html +++ b/deps/npm/docs/output/commands/npm-rebuild.html @@ -146,16 +146,10 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm rebuild [<package-spec>] ...] alias: rb </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>This command runs the <code>npm build</code> command on the matched folders. This is useful when you install a new version of node, and must recompile all your @@ -165,9 +159,6 @@ packages to build and/or link bins.</p> <p>If one or more package specs are provided, then only packages with a name and version matching one of the specifiers will be rebuilt.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="global"><code>global</code></h4> <ul> <li>Default: false</li> @@ -182,8 +173,6 @@ of the current working directory.</li> <li>bin files are linked to <code>{prefix}/bin</code></li> <li>man pages are linked to <code>{prefix}/share/man</code></li> </ul> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="bin-links"><code>bin-links</code></h4> <ul> <li>Default: true</li> @@ -194,8 +183,6 @@ executables.</p> <p>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.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="foreground-scripts"><code>foreground-scripts</code></h4> <ul> <li>Default: false</li> @@ -206,8 +193,6 @@ scripts for installed packages in the foreground process, sharing standard input, output, and error with the main npm process.</p> <p>Note that this will generally make installs run slower, and be much noisier, but can be useful for debugging.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="ignore-scripts"><code>ignore-scripts</code></h4> <ul> <li>Default: false</li> @@ -218,8 +203,6 @@ but can be useful for debugging.</p> <code>npm start</code>, <code>npm stop</code>, <code>npm restart</code>, <code>npm test</code>, and <code>npm run-script</code> will still run their intended script if <code>ignore-scripts</code> is set, but they will <em>not</em> run any pre- or post-scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -239,8 +222,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -257,8 +238,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -269,8 +248,6 @@ other things (test, exec, publish, etc.) will operate on the root project, all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="install-links"><code>install-links</code></h4> <ul> <li>Default: false</li> @@ -279,9 +256,6 @@ the specified workspaces, and not on the root project.</p> <p>When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../using-npm/package-spec.html">package spec</a></li> diff --git a/deps/npm/docs/output/commands/npm-repo.html b/deps/npm/docs/output/commands/npm-repo.html index 24197ef0ea1..f9149eb12fd 100644 --- a/deps/npm/docs/output/commands/npm-repo.html +++ b/deps/npm/docs/output/commands/npm-repo.html @@ -146,23 +146,14 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm repo [<pkgname> [<pkgname> ...]] </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>This command tries to guess at the likely location of a package's repository URL, and then tries to open it using the <code>--browser</code> config param. If no package name is provided, it will search for a <code>package.json</code> in the current folder and use the <code>repository</code> property.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="browser"><code>browser</code></h4> <ul> <li>Default: OS X: <code>"open"</code>, Windows: <code>"start"</code>, Others: <code>"xdg-open"</code></li> @@ -172,16 +163,12 @@ in the current folder and use the <code>repository</code> property.</p> <p>Set to <code>false</code> to suppress browser behavior and instead print urls to terminal.</p> <p>Set to <code>true</code> to use default system URL opener.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="registry"><code>registry</code></h4> <ul> <li>Default: "<a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a>"</li> <li>Type: URL</li> </ul> <p>The base URL of the npm registry.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -201,8 +188,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -219,8 +204,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -231,9 +214,6 @@ other things (test, exec, publish, etc.) will operate on the root project, all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-docs.html">npm docs</a></li> diff --git a/deps/npm/docs/output/commands/npm-restart.html b/deps/npm/docs/output/commands/npm-restart.html index 0e39072664a..d2a98fb6cf5 100644 --- a/deps/npm/docs/output/commands/npm-restart.html +++ b/deps/npm/docs/output/commands/npm-restart.html @@ -146,14 +146,8 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm restart [-- <args>] </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>This restarts a project. It is equivalent to running <code>npm run-script restart</code>.</p> <p>If the current project has a <code>"restart"</code> script specified in @@ -176,9 +170,6 @@ npm command-line interface <li>postrestart</li> </ol> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="ignore-scripts"><code>ignore-scripts</code></h4> <ul> <li>Default: false</li> @@ -189,17 +180,12 @@ npm command-line interface <code>npm start</code>, <code>npm stop</code>, <code>npm restart</code>, <code>npm test</code>, and <code>npm run-script</code> will still run their intended script if <code>ignore-scripts</code> is set, but they will <em>not</em> run any pre- or post-scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="script-shell"><code>script-shell</code></h4> <ul> <li>Default: '/bin/sh' on POSIX systems, 'cmd.exe' on Windows</li> <li>Type: null or String</li> </ul> <p>The shell to use for scripts run with the <code>npm exec</code>, <code>npm run</code> and <code>npm init <package-spec></code> commands.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-run-script.html">npm run-script</a></li> diff --git a/deps/npm/docs/output/commands/npm-root.html b/deps/npm/docs/output/commands/npm-root.html index e0595fd8e76..adbd7aa66b9 100644 --- a/deps/npm/docs/output/commands/npm-root.html +++ b/deps/npm/docs/output/commands/npm-root.html @@ -146,14 +146,8 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm root </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>Print the effective <code>node_modules</code> folder to standard out.</p> <p>Useful for using npm in shell scripts that do things with the @@ -163,9 +157,6 @@ global_node_modules="$(npm root --global)" echo "Global packages installed in: ${global_node_modules}" </code></pre> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="global"><code>global</code></h4> <ul> <li>Default: false</li> @@ -180,9 +171,6 @@ of the current working directory.</li> <li>bin files are linked to <code>{prefix}/bin</code></li> <li>man pages are linked to <code>{prefix}/share/man</code></li> </ul> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-prefix.html">npm prefix</a></li> diff --git a/deps/npm/docs/output/commands/npm-run-script.html b/deps/npm/docs/output/commands/npm-run-script.html index 5b1150cf4b9..f0aa6408e02 100644 --- a/deps/npm/docs/output/commands/npm-run-script.html +++ b/deps/npm/docs/output/commands/npm-run-script.html @@ -146,16 +146,10 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm run-script <command> [-- <args>] aliases: run, rum, urn </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>This runs an arbitrary command from a package's <code>"scripts"</code> object. If no <code>"command"</code> is provided, it will list the available scripts.</p> @@ -239,9 +233,6 @@ shorthand, e.g:</p> <p>This last command will run <code>test</code> in both <code>./packages/a</code> and <code>./packages/b</code> packages.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -261,8 +252,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -279,8 +268,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -291,8 +278,6 @@ other things (test, exec, publish, etc.) will operate on the root project, all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="if-present"><code>if-present</code></h4> <ul> <li>Default: false</li> @@ -305,8 +290,6 @@ it's present and fail if the script fails. This is useful, for example, when running scripts that may only apply for some builds in an otherwise generic CI setup.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="ignore-scripts"><code>ignore-scripts</code></h4> <ul> <li>Default: false</li> @@ -317,8 +300,6 @@ CI setup.</p> <code>npm start</code>, <code>npm stop</code>, <code>npm restart</code>, <code>npm test</code>, and <code>npm run-script</code> will still run their intended script if <code>ignore-scripts</code> is set, but they will <em>not</em> run any pre- or post-scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="foreground-scripts"><code>foreground-scripts</code></h4> <ul> <li>Default: false</li> @@ -329,17 +310,12 @@ scripts for installed packages in the foreground process, sharing standard input, output, and error with the main npm process.</p> <p>Note that this will generally make installs run slower, and be much noisier, but can be useful for debugging.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="script-shell"><code>script-shell</code></h4> <ul> <li>Default: '/bin/sh' on POSIX systems, 'cmd.exe' on Windows</li> <li>Type: null or String</li> </ul> <p>The shell to use for scripts run with the <code>npm exec</code>, <code>npm run</code> and <code>npm init <package-spec></code> commands.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../using-npm/scripts.html">npm scripts</a></li> diff --git a/deps/npm/docs/output/commands/npm-search.html b/deps/npm/docs/output/commands/npm-search.html index 4976e2d8a63..5a2f6126e02 100644 --- a/deps/npm/docs/output/commands/npm-search.html +++ b/deps/npm/docs/output/commands/npm-search.html @@ -146,16 +146,10 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm search [search terms ...] aliases: find, s, se </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>Note: This command is unaware of workspaces.</p> <h3 id="description">Description</h3> <p>Search the registry for packages matching the search terms. <code>npm search</code> @@ -176,17 +170,12 @@ and supports standard JavaScript RegExp syntax. In this case search will ignore a trailing <code>/</code> . (Note you must escape or quote many regular expression characters in most shells.)</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="long"><code>long</code></h4> <ul> <li>Default: false</li> <li>Type: Boolean</li> </ul> <p>Show extended information in <code>ls</code>, <code>search</code>, and <code>help-search</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="json"><code>json</code></h4> <ul> <li>Default: false</li> @@ -198,8 +187,6 @@ expression characters in most shells.)</p> saving them to your <code>package.json</code>.</li> </ul> <p>Not supported by all npm commands.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="color"><code>color</code></h4> <ul> <li>Default: true unless the NO_COLOR environ is set to something other than '0'</li> @@ -207,8 +194,6 @@ saving them to your <code>package.json</code>.</li> </ul> <p>If false, never shows colors. If <code>"always"</code> then always shows colors. If true, then only prints color codes for tty file descriptors.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="parseable"><code>parseable</code></h4> <ul> <li>Default: false</li> @@ -216,40 +201,30 @@ true, then only prints color codes for tty file descriptors.</p> </ul> <p>Output parseable results from commands that write to standard output. For <code>npm search</code>, this will be tab-separated table format.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="description2"><code>description</code></h4> <ul> <li>Default: true</li> <li>Type: Boolean</li> </ul> <p>Show the description in <code>npm search</code></p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="searchopts"><code>searchopts</code></h4> <ul> <li>Default: ""</li> <li>Type: String</li> </ul> <p>Space-separated options that are always passed to search.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="searchexclude"><code>searchexclude</code></h4> <ul> <li>Default: ""</li> <li>Type: String</li> </ul> <p>Space-separated options that limit the results from search.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="registry"><code>registry</code></h4> <ul> <li>Default: "<a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a>"</li> <li>Type: URL</li> </ul> <p>The base URL of the npm registry.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="prefer-online"><code>prefer-online</code></h4> <ul> <li>Default: false</li> @@ -257,8 +232,6 @@ true, then only prints color codes for tty file descriptors.</p> </ul> <p>If true, staleness checks for cached data will be forced, making the CLI look for updates immediately even for fresh package data.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="prefer-offline"><code>prefer-offline</code></h4> <ul> <li>Default: false</li> @@ -267,8 +240,6 @@ look for updates immediately even for fresh package data.</p> <p>If true, staleness checks for cached data will be bypassed, but missing data will be requested from the server. To force full offline mode, use <code>--offline</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="offline"><code>offline</code></h4> <ul> <li>Default: false</li> @@ -276,9 +247,6 @@ will be requested from the server. To force full offline mode, use </ul> <p>Force offline mode: no network requests will be done during install. To allow the CLI to fill in missing cache data, see <code>--prefer-offline</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../using-npm/registry.html">npm registry</a></li> diff --git a/deps/npm/docs/output/commands/npm-set-script.html b/deps/npm/docs/output/commands/npm-set-script.html index d9bc6b60771..7380f7abdbe 100644 --- a/deps/npm/docs/output/commands/npm-set-script.html +++ b/deps/npm/docs/output/commands/npm-set-script.html @@ -148,14 +148,8 @@ npm command-line interface <div id="_content"><h3 id="synopsis">Synopsis</h3> <p>An npm command that lets you create a task in the <code>scripts</code> section of the <code>package.json</code>.</p> <p>Deprecated.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm set-script [<script>] [<command>] </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p><strong>Example:</strong></p> <ul> <li><code>npm set-script start "http-server ."</code></li> @@ -169,9 +163,6 @@ npm command-line interface } </code></pre> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -191,8 +182,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -209,8 +198,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -221,9 +208,6 @@ other things (test, exec, publish, etc.) will operate on the root project, all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-run-script.html">npm run-script</a></li> diff --git a/deps/npm/docs/output/commands/npm-shrinkwrap.html b/deps/npm/docs/output/commands/npm-shrinkwrap.html index 26e8299586f..ff2926fe4bd 100644 --- a/deps/npm/docs/output/commands/npm-shrinkwrap.html +++ b/deps/npm/docs/output/commands/npm-shrinkwrap.html @@ -146,14 +146,8 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm shrinkwrap </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>Note: This command is unaware of workspaces.</p> <h3 id="description">Description</h3> <p>This command repurposes <code>package-lock.json</code> into a publishable diff --git a/deps/npm/docs/output/commands/npm-star.html b/deps/npm/docs/output/commands/npm-star.html index d442e391108..a0d1645a78f 100644 --- a/deps/npm/docs/output/commands/npm-star.html +++ b/deps/npm/docs/output/commands/npm-star.html @@ -146,14 +146,8 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm star [<package-spec>...] </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>Note: This command is unaware of workspaces.</p> <h3 id="description">Description</h3> <p>"Starring" a package means that you have some interest in it. It's @@ -167,17 +161,12 @@ a vaguely positive way to show that you care.</p> <h4 id="listing-stars">Listing stars</h4> <p>You can see all your starred packages using <a href="../commands/npm-stars.html"><code>npm stars</code></a></p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="registry"><code>registry</code></h4> <ul> <li>Default: "<a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a>"</li> <li>Type: URL</li> </ul> <p>The base URL of the npm registry.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="unicode"><code>unicode</code></h4> <ul> <li>Default: false on windows, true on mac/unix systems with a unicode locale, @@ -186,8 +175,6 @@ as defined by the <code>LC_ALL</code>, <code>LC_CTYPE</code>, or <code>LANG</cod </ul> <p>When set to true, npm uses unicode characters in the tree output. When false, it uses ascii characters instead of unicode glyphs.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="otp"><code>otp</code></h4> <ul> <li>Default: null</li> @@ -197,9 +184,6 @@ false, it uses ascii characters instead of unicode glyphs.</p> when publishing or changing package permissions with <code>npm access</code>.</p> <p>If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../using-npm/package-spec.html">package spec</a></li> diff --git a/deps/npm/docs/output/commands/npm-stars.html b/deps/npm/docs/output/commands/npm-stars.html index d4626066c43..e7c06d7b826 100644 --- a/deps/npm/docs/output/commands/npm-stars.html +++ b/deps/npm/docs/output/commands/npm-stars.html @@ -146,14 +146,8 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm stars [<user>] </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>Note: This command is unaware of workspaces.</p> <h3 id="description">Description</h3> <p>If you have starred a lot of neat things and want to find them again @@ -161,18 +155,12 @@ quickly this command lets you do just that.</p> <p>You may also want to see your friend's favorite packages, in this case you will most certainly enjoy this command.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="registry"><code>registry</code></h4> <ul> <li>Default: "<a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a>"</li> <li>Type: URL</li> </ul> <p>The base URL of the npm registry.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-star.html">npm star</a></li> diff --git a/deps/npm/docs/output/commands/npm-start.html b/deps/npm/docs/output/commands/npm-start.html index 4f300f37ade..39adb76074c 100644 --- a/deps/npm/docs/output/commands/npm-start.html +++ b/deps/npm/docs/output/commands/npm-start.html @@ -146,14 +146,8 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm start [-- <args>] </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>This runs a predefined command specified in the <code>"start"</code> property of a package's <code>"scripts"</code> object.</p> @@ -180,9 +174,6 @@ use custom arguments when executing scripts. Refer to <a href="../commands/npm-r </code></pre> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="ignore-scripts"><code>ignore-scripts</code></h4> <ul> <li>Default: false</li> @@ -193,17 +184,12 @@ use custom arguments when executing scripts. Refer to <a href="../commands/npm-r <code>npm start</code>, <code>npm stop</code>, <code>npm restart</code>, <code>npm test</code>, and <code>npm run-script</code> will still run their intended script if <code>ignore-scripts</code> is set, but they will <em>not</em> run any pre- or post-scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="script-shell"><code>script-shell</code></h4> <ul> <li>Default: '/bin/sh' on POSIX systems, 'cmd.exe' on Windows</li> <li>Type: null or String</li> </ul> <p>The shell to use for scripts run with the <code>npm exec</code>, <code>npm run</code> and <code>npm init <package-spec></code> commands.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-run-script.html">npm run-script</a></li> diff --git a/deps/npm/docs/output/commands/npm-stop.html b/deps/npm/docs/output/commands/npm-stop.html index 8c91c7321a5..11fda3e15c3 100644 --- a/deps/npm/docs/output/commands/npm-stop.html +++ b/deps/npm/docs/output/commands/npm-stop.html @@ -146,14 +146,8 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm stop [-- <args>] </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>This runs a predefined command specified in the "stop" property of a package's "scripts" object.</p> @@ -175,9 +169,6 @@ that will run if the <code>"stop"</code> property is not defined.</p> </code></pre> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="ignore-scripts"><code>ignore-scripts</code></h4> <ul> <li>Default: false</li> @@ -188,17 +179,12 @@ that will run if the <code>"stop"</code> property is not defined.</p> <code>npm start</code>, <code>npm stop</code>, <code>npm restart</code>, <code>npm test</code>, and <code>npm run-script</code> will still run their intended script if <code>ignore-scripts</code> is set, but they will <em>not</em> run any pre- or post-scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="script-shell"><code>script-shell</code></h4> <ul> <li>Default: '/bin/sh' on POSIX systems, 'cmd.exe' on Windows</li> <li>Type: null or String</li> </ul> <p>The shell to use for scripts run with the <code>npm exec</code>, <code>npm run</code> and <code>npm init <package-spec></code> commands.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-run-script.html">npm run-script</a></li> diff --git a/deps/npm/docs/output/commands/npm-team.html b/deps/npm/docs/output/commands/npm-team.html index a7b99172927..07b31a7cfa6 100644 --- a/deps/npm/docs/output/commands/npm-team.html +++ b/deps/npm/docs/output/commands/npm-team.html @@ -146,18 +146,12 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm team create <scope:team> [--otp <otpcode>] npm team destroy <scope:team> [--otp <otpcode>] npm team add <scope:team> <user> [--otp <otpcode>] npm team rm <scope:team> <user> [--otp <otpcode>] npm team ls <scope>|<scope:team> </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>Note: This command is unaware of workspaces.</p> <h3 id="description">Description</h3> <p>Used to manage teams in organizations, and change team memberships. Does not @@ -222,17 +216,12 @@ is done through the website, not the npm CLI.</p> <p>To use teams to manage permissions on packages belonging to your organization, use the <code>npm access</code> command to grant or revoke the appropriate permissions.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="registry"><code>registry</code></h4> <ul> <li>Default: "<a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a>"</li> <li>Type: URL</li> </ul> <p>The base URL of the npm registry.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="otp"><code>otp</code></h4> <ul> <li>Default: null</li> @@ -242,8 +231,6 @@ use the <code>npm access</code> command to grant or revoke the appropriate permi when publishing or changing package permissions with <code>npm access</code>.</p> <p>If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="parseable"><code>parseable</code></h4> <ul> <li>Default: false</li> @@ -251,8 +238,6 @@ password, npm will prompt on the command line for one.</p> </ul> <p>Output parseable results from commands that write to standard output. For <code>npm search</code>, this will be tab-separated table format.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="json"><code>json</code></h4> <ul> <li>Default: false</li> @@ -264,9 +249,6 @@ password, npm will prompt on the command line for one.</p> saving them to your <code>package.json</code>.</li> </ul> <p>Not supported by all npm commands.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-access.html">npm access</a></li> diff --git a/deps/npm/docs/output/commands/npm-test.html b/deps/npm/docs/output/commands/npm-test.html index c4d71b30f51..b9a79dd9cfd 100644 --- a/deps/npm/docs/output/commands/npm-test.html +++ b/deps/npm/docs/output/commands/npm-test.html @@ -146,16 +146,10 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm test [-- <args>] aliases: tst, t </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>This runs a predefined command specified in the <code>"test"</code> property of a package's <code>"scripts"</code> object.</p> @@ -173,9 +167,6 @@ a package's <code>"scripts"</code> object.</p> (test.js output would be here) </code></pre> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="ignore-scripts"><code>ignore-scripts</code></h4> <ul> <li>Default: false</li> @@ -186,17 +177,12 @@ a package's <code>"scripts"</code> object.</p> <code>npm start</code>, <code>npm stop</code>, <code>npm restart</code>, <code>npm test</code>, and <code>npm run-script</code> will still run their intended script if <code>ignore-scripts</code> is set, but they will <em>not</em> run any pre- or post-scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="script-shell"><code>script-shell</code></h4> <ul> <li>Default: '/bin/sh' on POSIX systems, 'cmd.exe' on Windows</li> <li>Type: null or String</li> </ul> <p>The shell to use for scripts run with the <code>npm exec</code>, <code>npm run</code> and <code>npm init <package-spec></code> commands.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-run-script.html">npm run-script</a></li> diff --git a/deps/npm/docs/output/commands/npm-token.html b/deps/npm/docs/output/commands/npm-token.html index 8ce05427c6c..fb9bd301bb4 100644 --- a/deps/npm/docs/output/commands/npm-token.html +++ b/deps/npm/docs/output/commands/npm-token.html @@ -146,16 +146,10 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm token list npm token revoke <id|token> npm token create [--read-only] [--cidr=list] </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>Note: This command is unaware of workspaces.</p> <h3 id="description">Description</h3> <p>This lets you list, create and revoke authentication tokens.</p> @@ -217,9 +211,6 @@ output of <code>npm token list</code>. This will NOT accept the truncated token found in the normal <code>npm token list</code> output.</li> </ul> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="read-only"><code>read-only</code></h4> <ul> <li>Default: false</li> @@ -227,8 +218,6 @@ found in the normal <code>npm token list</code> output.</li> </ul> <p>This is used to mark a token as unable to publish when configuring limited access tokens with the <code>npm token create</code> command.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="cidr"><code>cidr</code></h4> <ul> <li>Default: null</li> @@ -236,16 +225,12 @@ access tokens with the <code>npm token create</code> command.</p> </ul> <p>This is a list of CIDR address to be used when configuring limited access tokens with the <code>npm token create</code> command.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="registry"><code>registry</code></h4> <ul> <li>Default: "<a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a>"</li> <li>Type: URL</li> </ul> <p>The base URL of the npm registry.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="otp"><code>otp</code></h4> <ul> <li>Default: null</li> @@ -255,9 +240,6 @@ tokens with the <code>npm token create</code> command.</p> when publishing or changing package permissions with <code>npm access</code>.</p> <p>If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-adduser.html">npm adduser</a></li> diff --git a/deps/npm/docs/output/commands/npm-uninstall.html b/deps/npm/docs/output/commands/npm-uninstall.html index 9823201dbc8..179e181af57 100644 --- a/deps/npm/docs/output/commands/npm-uninstall.html +++ b/deps/npm/docs/output/commands/npm-uninstall.html @@ -146,16 +146,10 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm uninstall [<@scope>/]<pkg>... aliases: unlink, remove, rm, r, un </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>This uninstalls a package, completely removing everything npm installed on its behalf.</p> @@ -184,9 +178,6 @@ it uninstalls the current package context as a global package. <p><code>lodash</code> will not be removed from your <code>package.json</code>, <code>npm-shrinkwrap.json</code>, or <code>package-lock.json</code> files.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="save"><code>save</code></h4> <ul> <li>Default: <code>true</code> unless when using <code>npm update</code> where it defaults to <code>false</code></li> @@ -196,8 +187,6 @@ it uninstalls the current package context as a global package. <p>When used with the <code>npm rm</code> command, removes the dependency from <code>package.json</code>.</p> <p>Will also prevent writing to <code>package-lock.json</code> if set to <code>false</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -217,8 +206,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -235,8 +222,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -247,8 +232,6 @@ other things (test, exec, publish, etc.) will operate on the root project, all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="install-links"><code>install-links</code></h4> <ul> <li>Default: false</li> @@ -257,9 +240,6 @@ the specified workspaces, and not on the root project.</p> <p>When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-prune.html">npm prune</a></li> diff --git a/deps/npm/docs/output/commands/npm-unpublish.html b/deps/npm/docs/output/commands/npm-unpublish.html index ab5858f2666..0e143e1e0e0 100644 --- a/deps/npm/docs/output/commands/npm-unpublish.html +++ b/deps/npm/docs/output/commands/npm-unpublish.html @@ -146,14 +146,8 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm unpublish [<package-spec>] </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>To learn more about how the npm registry treats unpublish, see our <!-- raw HTML omitted --> unpublish policies<!-- raw HTML omitted --></p> <h3 id="warning">Warning</h3> <p>Consider using the <a href="../commands/npm-deprecate.html"><code>deprecate</code></a> command instead, @@ -172,9 +166,6 @@ you must use a new version number. If you unpublish the entire package, you may not publish any new versions of that package until 24 hours have passed.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="dry-run"><code>dry-run</code></h4> <ul> <li>Default: false</li> @@ -186,8 +177,6 @@ commands that modify your local installation, eg, <code>install</code>, <code>up <code>dedupe</code>, <code>uninstall</code>, as well as <code>pack</code> and <code>publish</code>.</p> <p>Note: This is NOT honored by other network related commands, eg <code>dist-tags</code>, <code>owner</code>, etc.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="force"><code>force</code></h4> <ul> <li>Default: false</li> @@ -213,8 +202,6 @@ range (including SemVer-major changes).</li> </ul> <p>If you don't have a clear idea of what you want to do, it is strongly recommended that you do not use this option!</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -234,8 +221,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -252,9 +237,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../using-npm/package-spec.html">package spec</a></li> diff --git a/deps/npm/docs/output/commands/npm-unstar.html b/deps/npm/docs/output/commands/npm-unstar.html index c8b057f8e2d..ccc495c20ee 100644 --- a/deps/npm/docs/output/commands/npm-unstar.html +++ b/deps/npm/docs/output/commands/npm-unstar.html @@ -146,14 +146,8 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm unstar [<package-spec>...] </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>Note: This command is unaware of workspaces.</p> <h3 id="description">Description</h3> <p>"Unstarring" a package is the opposite of <a href="../commands/npm-star.html"><code>npm star</code></a>, @@ -165,17 +159,12 @@ it removes an item from your list of favorite packages.</p> <h4 id="listing-stars">Listing stars</h4> <p>You can see all your starred packages using <a href="../commands/npm-stars.html"><code>npm stars</code></a></p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="registry"><code>registry</code></h4> <ul> <li>Default: "<a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a>"</li> <li>Type: URL</li> </ul> <p>The base URL of the npm registry.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="unicode"><code>unicode</code></h4> <ul> <li>Default: false on windows, true on mac/unix systems with a unicode locale, @@ -184,8 +173,6 @@ as defined by the <code>LC_ALL</code>, <code>LC_CTYPE</code>, or <code>LANG</cod </ul> <p>When set to true, npm uses unicode characters in the tree output. When false, it uses ascii characters instead of unicode glyphs.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="otp"><code>otp</code></h4> <ul> <li>Default: null</li> @@ -195,9 +182,6 @@ false, it uses ascii characters instead of unicode glyphs.</p> when publishing or changing package permissions with <code>npm access</code>.</p> <p>If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-star.html">npm star</a></li> diff --git a/deps/npm/docs/output/commands/npm-update.html b/deps/npm/docs/output/commands/npm-update.html index d88ea8578ba..89f7de9a5a7 100644 --- a/deps/npm/docs/output/commands/npm-update.html +++ b/deps/npm/docs/output/commands/npm-update.html @@ -146,16 +146,10 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm update [<pkg>...] aliases: up, upgrade, udpate </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>This command will update all the packages listed to the latest version (specified by the <code>tag</code> config), respecting the semver constraints of @@ -257,9 +251,6 @@ need to run <code>npm install -g [<pkg>...]</code></p> <p>NOTE: If a package has been upgraded to a version newer than <code>latest</code>, it will be <em>downgraded</em>.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="save"><code>save</code></h4> <ul> <li>Default: <code>true</code> unless when using <code>npm update</code> where it defaults to <code>false</code></li> @@ -269,8 +260,6 @@ be <em>downgraded</em>.</p> <p>When used with the <code>npm rm</code> command, removes the dependency from <code>package.json</code>.</p> <p>Will also prevent writing to <code>package-lock.json</code> if set to <code>false</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="global"><code>global</code></h4> <ul> <li>Default: false</li> @@ -285,8 +274,6 @@ of the current working directory.</li> <li>bin files are linked to <code>{prefix}/bin</code></li> <li>man pages are linked to <code>{prefix}/share/man</code></li> </ul> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="global-style"><code>global-style</code></h4> <ul> <li>Default: false</li> @@ -298,8 +285,6 @@ direct dependencies will show in <code>node_modules</code> and everything they d on will be flattened in their <code>node_modules</code> folders. This obviously will eliminate some deduping. If used with <code>legacy-bundling</code>, <code>legacy-bundling</code> will be preferred.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="legacy-bundling"><code>legacy-bundling</code></h4> <ul> <li>Default: false</li> @@ -309,8 +294,6 @@ will be preferred.</p> such as the one included with node 0.8, can install the package. This eliminates all automatic deduping. If used with <code>global-style</code> this option will be preferred.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="omit"><code>omit</code></h4> <ul> <li>Default: 'dev' if the <code>NODE_ENV</code> environment variable is set to @@ -325,8 +308,6 @@ physically installed on disk.</p> it will be included.</p> <p>If the resulting omit list includes <code>'dev'</code>, then the <code>NODE_ENV</code> environment variable will be set to <code>'production'</code> for all lifecycle scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="strict-peer-deps"><code>strict-peer-deps</code></h4> <ul> <li>Default: false</li> @@ -343,8 +324,6 @@ the range set in their package's <code>peerDependencies</code> object.</p> <p>When such and override is performed, a warning is printed, explaining the conflict and the packages involved. If <code>--strict-peer-deps</code> is set, then this warning is treated as a failure.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="package-lock"><code>package-lock</code></h4> <ul> <li>Default: true</li> @@ -353,8 +332,6 @@ this warning is treated as a failure.</p> <p>If set to false, then ignore <code>package-lock.json</code> files when installing. This will also prevent <em>writing</em> <code>package-lock.json</code> if <code>save</code> is true.</p> <p>This configuration does not affect <code>npm ci</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="foreground-scripts"><code>foreground-scripts</code></h4> <ul> <li>Default: false</li> @@ -365,8 +342,6 @@ scripts for installed packages in the foreground process, sharing standard input, output, and error with the main npm process.</p> <p>Note that this will generally make installs run slower, and be much noisier, but can be useful for debugging.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="ignore-scripts"><code>ignore-scripts</code></h4> <ul> <li>Default: false</li> @@ -377,8 +352,6 @@ but can be useful for debugging.</p> <code>npm start</code>, <code>npm stop</code>, <code>npm restart</code>, <code>npm test</code>, and <code>npm run-script</code> will still run their intended script if <code>ignore-scripts</code> is set, but they will <em>not</em> run any pre- or post-scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="audit"><code>audit</code></h4> <ul> <li>Default: true</li> @@ -388,8 +361,6 @@ will <em>not</em> run any pre- or post-scripts.</p> default registry and all registries configured for scopes. See the documentation for <a href="../commands/npm-audit.html"><code>npm audit</code></a> for details on what is submitted.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="bin-links"><code>bin-links</code></h4> <ul> <li>Default: true</li> @@ -400,8 +371,6 @@ executables.</p> <p>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.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="fund"><code>fund</code></h4> <ul> <li>Default: true</li> @@ -409,8 +378,6 @@ systems.</p> </ul> <p>When "true" displays the message at the end of each <code>npm install</code> acknowledging the number of dependencies looking for funding. See <a href="../commands/npm-fund.html"><code>npm fund</code></a> for details.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="dry-run"><code>dry-run</code></h4> <ul> <li>Default: false</li> @@ -422,8 +389,6 @@ commands that modify your local installation, eg, <code>install</code>, <code>up <code>dedupe</code>, <code>uninstall</code>, as well as <code>pack</code> and <code>publish</code>.</p> <p>Note: This is NOT honored by other network related commands, eg <code>dist-tags</code>, <code>owner</code>, etc.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -443,8 +408,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -461,8 +424,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -473,8 +434,6 @@ other things (test, exec, publish, etc.) will operate on the root project, all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="install-links"><code>install-links</code></h4> <ul> <li>Default: false</li> @@ -483,9 +442,6 @@ the specified workspaces, and not on the root project.</p> <p>When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-install.html">npm install</a></li> diff --git a/deps/npm/docs/output/commands/npm-version.html b/deps/npm/docs/output/commands/npm-version.html index 3bab12fec16..3806d08460a 100644 --- a/deps/npm/docs/output/commands/npm-version.html +++ b/deps/npm/docs/output/commands/npm-version.html @@ -146,20 +146,11 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm version [<newversion> | major | minor | patch | premajor | preminor | prepatch | prerelease | from-git] alias: verison </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="allow-same-version"><code>allow-same-version</code></h4> <ul> <li>Default: false</li> @@ -167,16 +158,12 @@ alias: verison </ul> <p>Prevents throwing an error when <code>npm version</code> is used to set the new version to the same value as the current version.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="commit-hooks"><code>commit-hooks</code></h4> <ul> <li>Default: true</li> <li>Type: Boolean</li> </ul> <p>Run git commit hooks when using the <code>npm version</code> command.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="git-tag-version"><code>git-tag-version</code></h4> <ul> <li>Default: true</li> @@ -184,8 +171,6 @@ to the same value as the current version.</p> </ul> <p>Tag the commit when using the <code>npm version</code> command. Setting this to false results in no commit being made at all.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="json"><code>json</code></h4> <ul> <li>Default: false</li> @@ -197,8 +182,6 @@ results in no commit being made at all.</p> saving them to your <code>package.json</code>.</li> </ul> <p>Not supported by all npm commands.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="preid"><code>preid</code></h4> <ul> <li>Default: ""</li> @@ -206,8 +189,6 @@ saving them to your <code>package.json</code>.</li> </ul> <p>The "prerelease identifier" to use as a prefix for the "prerelease" part of a semver. Like the <code>rc</code> in <code>1.2.0-rc.8</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="sign-git-tag"><code>sign-git-tag</code></h4> <ul> <li>Default: false</li> @@ -217,8 +198,6 @@ a semver. Like the <code>rc</code> in <code>1.2.0-rc.8</code>.</p> <code>-s</code> to add a signature.</p> <p>Note that git requires you to have set up GPG keys in your git configs for this to work properly.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -238,8 +217,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -256,8 +233,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces-update"><code>workspaces-update</code></h4> <ul> <li>Default: true</li> @@ -265,8 +240,6 @@ other things (test, exec, publish, etc.) will operate on the root project, </ul> <p>If set to true, the npm cli will run an update after operations that may possibly change the workspaces installed to the <code>node_modules</code> folder.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -277,9 +250,6 @@ possibly change the workspaces installed to the <code>node_modules</code> folder all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>Run this in a package directory to bump the version and write the new data back to <code>package.json</code>, <code>package-lock.json</code>, and, if present, diff --git a/deps/npm/docs/output/commands/npm-view.html b/deps/npm/docs/output/commands/npm-view.html index 2b74e28f3b9..6dc1a973908 100644 --- a/deps/npm/docs/output/commands/npm-view.html +++ b/deps/npm/docs/output/commands/npm-view.html @@ -146,16 +146,10 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm view [<package-spec>] [<field>[.subfield]...] aliases: info, show, v </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>This command shows data about a package and prints it to stdout.</p> <p>As an example, to view information about the <code>connect</code> package from the registry, you would run:</p> @@ -206,9 +200,6 @@ this:</p> <pre lang="bash"><code>npm view connect versions </code></pre> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="json"><code>json</code></h4> <ul> <li>Default: false</li> @@ -220,8 +211,6 @@ this:</p> saving them to your <code>package.json</code>.</li> </ul> <p>Not supported by all npm commands.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -241,8 +230,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -259,8 +246,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -271,9 +256,6 @@ other things (test, exec, publish, etc.) will operate on the root project, all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="output">Output</h3> <p>If only a single string field for a single version is output, then it will not be colorized or quoted, to enable piping the output to diff --git a/deps/npm/docs/output/commands/npm-whoami.html b/deps/npm/docs/output/commands/npm-whoami.html index 1561991a458..35a0b00119e 100644 --- a/deps/npm/docs/output/commands/npm-whoami.html +++ b/deps/npm/docs/output/commands/npm-whoami.html @@ -146,14 +146,8 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npm whoami </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>Note: This command is unaware of workspaces.</p> <h3 id="description">Description</h3> <p>Display the npm username of the currently logged-in user.</p> @@ -163,18 +157,12 @@ associated with the token, and print to standard output.</p> <p>If logged into a registry that uses Basic Auth, then simply print the <code>username</code> portion of the authentication string.</p> <h3 id="configuration">Configuration</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="registry"><code>registry</code></h4> <ul> <li>Default: "<a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a>"</li> <li>Type: URL</li> </ul> <p>The base URL of the npm registry.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See Also</h3> <ul> <li><a href="../commands/npm-config.html">npm config</a></li> diff --git a/deps/npm/docs/output/commands/npm.html b/deps/npm/docs/output/commands/npm.html index 1be4ac89284..eddbc96a678 100644 --- a/deps/npm/docs/output/commands/npm.html +++ b/deps/npm/docs/output/commands/npm.html @@ -146,10 +146,10 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> +<pre lang="bash"><code>npm +</code></pre> <h3 id="version">Version</h3> -<p>8.19.2</p> +<p>8.19.3</p> <h3 id="description">Description</h3> <p>npm is the package manager for the Node JavaScript platform. It puts modules in place so that node can find them, and manages dependency diff --git a/deps/npm/docs/output/commands/npx.html b/deps/npm/docs/output/commands/npx.html index 2664dfe025b..795bc800755 100644 --- a/deps/npm/docs/output/commands/npx.html +++ b/deps/npm/docs/output/commands/npx.html @@ -146,17 +146,11 @@ npm command-line interface </section> <div id="_content"><h3 id="synopsis">Synopsis</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <pre lang="bash"><code>npx -- <pkg>[@<version>] [args...] npx --package=<pkg>[@<version>] -- <cmd> [args...] npx -c '<cmd> [args...]' npx --package=foo -c '<cmd> [args...]' </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="description">Description</h3> <p>This command allows you to run an arbitrary command from an npm package (either one installed locally, or fetched remotely), in a similar context diff --git a/deps/npm/docs/output/configuring-npm/package-json.html b/deps/npm/docs/output/configuring-npm/package-json.html index 7fdc03e3eaf..826d9369ef5 100644 --- a/deps/npm/docs/output/configuring-npm/package-json.html +++ b/deps/npm/docs/output/configuring-npm/package-json.html @@ -155,10 +155,9 @@ settings described in <a href="../using-npm/config.html"><code>config</code></a> <p>If you plan to publish your package, the <em>most</em> important things in your package.json are the name and version fields as they will be required. The name and version together form an identifier that is assumed to be -completely unique. Changes to the package should come along with changes -to the version. If you don't plan to publish your package, the name and -version fields are optional.</p> -<p>The name is what your thing is called.</p> +completely unique. If you don't plan to publish your package, the name and +version fields are optional. +The name field contains your package name.</p> <p>Some rules:</p> <ul> <li>The name must be less than or equal to 214 characters. This includes the @@ -185,12 +184,9 @@ that name already, before you get too attached to it. <p>A name can be optionally prefixed by a scope, e.g. <code>@myorg/mypackage</code>. See <a href="../using-npm/scope.html"><code>scope</code></a> for more detail.</p> <h3 id="version">version</h3> -<p>If you plan to publish your package, the <em>most</em> important things in your -package.json are the name and version fields as they will be required. The -name and version together form an identifier that is assumed to be -completely unique. Changes to the package should come along with changes -to the version. If you don't plan to publish your package, the name and -version fields are optional.</p> +<p>Changes to the package should come along with changes to the version. +You can show developers how much they need to adjust on a new update by +using <a href="../../about-semantic-versioning">semantic versioning</a></p> <p>Version must be parseable by <a href="https://github.com/npm/node-semver">node-semver</a>, which is bundled with npm as a dependency. (<code>npm install semver</code> to use it yourself.)</p> diff --git a/deps/npm/docs/output/using-npm/config.html b/deps/npm/docs/output/using-npm/config.html index 42880a27025..66c9f6fa131 100644 --- a/deps/npm/docs/output/using-npm/config.html +++ b/deps/npm/docs/output/using-npm/config.html @@ -186,9 +186,6 @@ CLI option <code>--globalconfig</code> or environment variable <code>$NPM_CONFIG internal to npm, and are defaults if nothing else is specified.</p> <h3 id="shorthands-and-other-cli-niceties">Shorthands and Other CLI Niceties</h3> <p>The following shorthands are parsed on the command-line:</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <ul> <li><code>-a</code>: <code>--all</code></li> <li><code>--enjoy-by</code>: <code>--before</code></li> @@ -231,9 +228,6 @@ internal to npm, and are defaults if nothing else is specified.</p> <li><code>--ws</code>: <code>--workspaces</code></li> <li><code>-y</code>: <code>--yes</code></li> </ul> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <p>If the specified configuration param resolves unambiguously to a known configuration parameter, then it is expanded to that configuration parameter. For example:</p> @@ -250,9 +244,6 @@ example:</p> npm ls --global --parseable --long --loglevel info </code></pre> <h3 id="config-settings">Config Settings</h3> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="auth"><code>_auth</code></h4> <ul> <li>Default: null</li> @@ -264,8 +255,6 @@ registries you will need to scope it like "//other-registry.tld/:_auth"</p> <p>Warning: This should generally not be set via a command-line option. It is safer to use a registry-provided authentication bearer token stored in the ~/.npmrc file by running <code>npm login</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="access"><code>access</code></h4> <ul> <li>Default: 'restricted' for scoped packages, 'public' for unscoped packages</li> @@ -280,8 +269,6 @@ the package access level on the initial publish of the package. Any subsequent <code>npm publish</code> commands using the <code>--access</code> flag will not have an effect to the access level. To make changes to the access level after the initial publish use <code>npm access</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="all"><code>all</code></h4> <ul> <li>Default: false</li> @@ -290,8 +277,6 @@ initial publish use <code>npm access</code>.</p> <p>When running <code>npm outdated</code> and <code>npm ls</code>, setting <code>--all</code> will show all outdated or installed packages, rather than only those directly depended upon by the current project.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="allow-same-version"><code>allow-same-version</code></h4> <ul> <li>Default: false</li> @@ -299,8 +284,6 @@ upon by the current project.</p> </ul> <p>Prevents throwing an error when <code>npm version</code> is used to set the new version to the same value as the current version.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="audit"><code>audit</code></h4> <ul> <li>Default: true</li> @@ -310,8 +293,6 @@ to the same value as the current version.</p> default registry and all registries configured for scopes. See the documentation for <a href="../commands/npm-audit.html"><code>npm audit</code></a> for details on what is submitted.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="audit-level"><code>audit-level</code></h4> <ul> <li>Default: null</li> @@ -319,8 +300,6 @@ submitted.</p> </ul> <p>The minimum level of vulnerability for <code>npm audit</code> to exit with a non-zero exit code.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="auth-type"><code>auth-type</code></h4> <ul> <li>Default: "legacy"</li> @@ -329,8 +308,6 @@ exit code.</p> <p>NOTE: auth-type values "sso", "saml", "oauth", and "webauthn" will be removed in a future version.</p> <p>What authentication strategy to use with <code>login</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="before"><code>before</code></h4> <ul> <li>Default: null</li> @@ -344,8 +321,6 @@ dependencies, the command will error.</p> <code>--before</code> filter, the most recent version less than or equal to that tag will be used. For example, <code>foo@latest</code> might install <code>foo@1.2</code> even though <code>latest</code> is <code>2.0</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="bin-links"><code>bin-links</code></h4> <ul> <li>Default: true</li> @@ -356,8 +331,6 @@ executables.</p> <p>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.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="browser"><code>browser</code></h4> <ul> <li>Default: OS X: <code>"open"</code>, Windows: <code>"start"</code>, Others: <code>"xdg-open"</code></li> @@ -367,8 +340,6 @@ systems.</p> <p>Set to <code>false</code> to suppress browser behavior and instead print urls to terminal.</p> <p>Set to <code>true</code> to use default system URL opener.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="ca"><code>ca</code></h4> <ul> <li>Default: null</li> @@ -387,16 +358,12 @@ trust only that specific signing authority.</p> ca[]="..." </code></pre> <p>See also the <code>strict-ssl</code> config.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="cache"><code>cache</code></h4> <ul> <li>Default: Windows: <code>%LocalAppData%\npm-cache</code>, Posix: <code>~/.npm</code></li> <li>Type: Path</li> </ul> <p>The location of npm's cache directory. See <a href="../commands/npm-cache.html"><code>npm cache</code></a></p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="cafile"><code>cafile</code></h4> <ul> <li>Default: null</li> @@ -405,8 +372,6 @@ ca[]="..." <p>A path to a file containing one or multiple Certificate Authority signing certificates. Similar to the <code>ca</code> setting, but allows for multiple CA's, as well as for the CA information to be stored in a file on disk.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="call"><code>call</code></h4> <ul> <li>Default: ""</li> @@ -416,8 +381,6 @@ well as for the CA information to be stored in a file on disk.</p> custom command to be run along with the installed packages.</p> <pre lang="bash"><code>npm exec --package yo --package generator-node --call "yo node" </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="cert"><code>cert</code></h4> <ul> <li>Default: null</li> @@ -431,8 +394,6 @@ newlines replaced by the string "\n". For example:</p> <p>It is <em>not</em> the path to a certificate file, though you can set a registry-scoped "certfile" path like "//other-registry.tld/:certfile=/path/to/cert.pem".</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="ci-name"><code>ci-name</code></h4> <ul> <li>Default: The name of the current CI system, or <code>null</code> when not on a known CI @@ -442,8 +403,6 @@ platform.</li> <p>The name of a continuous integration system. If not set explicitly, npm will detect the current CI environment using the <a href="http://npm.im/@npmcli/ci-detect"><code>@npmcli/ci-detect</code></a> module.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="cidr"><code>cidr</code></h4> <ul> <li>Default: null</li> @@ -451,8 +410,6 @@ detect the current CI environment using the </ul> <p>This is a list of CIDR address to be used when configuring limited access tokens with the <code>npm token create</code> command.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="color"><code>color</code></h4> <ul> <li>Default: true unless the NO_COLOR environ is set to something other than '0'</li> @@ -460,16 +417,12 @@ tokens with the <code>npm token create</code> command.</p> </ul> <p>If false, never shows colors. If <code>"always"</code> then always shows colors. If true, then only prints color codes for tty file descriptors.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="commit-hooks"><code>commit-hooks</code></h4> <ul> <li>Default: true</li> <li>Type: Boolean</li> </ul> <p>Run git commit hooks when using the <code>npm version</code> command.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="depth"><code>depth</code></h4> <ul> <li>Default: <code>Infinity</code> if <code>--all</code> is set, otherwise <code>1</code></li> @@ -478,48 +431,36 @@ true, then only prints color codes for tty file descriptors.</p> <p>The depth to go when recursing packages for <code>npm ls</code>.</p> <p>If not set, <code>npm ls</code> will show only the immediate dependencies of the root project. If <code>--all</code> is set, then npm will show all dependencies by default.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="description2"><code>description</code></h4> <ul> <li>Default: true</li> <li>Type: Boolean</li> </ul> <p>Show the description in <code>npm search</code></p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="diff"><code>diff</code></h4> <ul> <li>Default:</li> <li>Type: String (can be set multiple times)</li> </ul> <p>Define arguments to compare in <code>npm diff</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="diff-dst-prefix"><code>diff-dst-prefix</code></h4> <ul> <li>Default: "b/"</li> <li>Type: String</li> </ul> <p>Destination prefix to be used in <code>npm diff</code> output.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="diff-ignore-all-space"><code>diff-ignore-all-space</code></h4> <ul> <li>Default: false</li> <li>Type: Boolean</li> </ul> <p>Ignore whitespace when comparing lines in <code>npm diff</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="diff-name-only"><code>diff-name-only</code></h4> <ul> <li>Default: false</li> <li>Type: Boolean</li> </ul> <p>Prints only filenames when using <code>npm diff</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="diff-no-prefix"><code>diff-no-prefix</code></h4> <ul> <li>Default: false</li> @@ -528,32 +469,24 @@ project. If <code>--all</code> is set, then npm will show all dependencies by de <p>Do not show any source or destination prefix in <code>npm diff</code> output.</p> <p>Note: this causes <code>npm diff</code> to ignore the <code>--diff-src-prefix</code> and <code>--diff-dst-prefix</code> configs.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="diff-src-prefix"><code>diff-src-prefix</code></h4> <ul> <li>Default: "a/"</li> <li>Type: String</li> </ul> <p>Source prefix to be used in <code>npm diff</code> output.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="diff-text"><code>diff-text</code></h4> <ul> <li>Default: false</li> <li>Type: Boolean</li> </ul> <p>Treat all files as text in <code>npm diff</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="diff-unified"><code>diff-unified</code></h4> <ul> <li>Default: 3</li> <li>Type: Number</li> </ul> <p>The number of lines of context to print in <code>npm diff</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="dry-run"><code>dry-run</code></h4> <ul> <li>Default: false</li> @@ -565,8 +498,6 @@ commands that modify your local installation, eg, <code>install</code>, <code>up <code>dedupe</code>, <code>uninstall</code>, as well as <code>pack</code> and <code>publish</code>.</p> <p>Note: This is NOT honored by other network related commands, eg <code>dist-tags</code>, <code>owner</code>, etc.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="editor"><code>editor</code></h4> <ul> <li>Default: The EDITOR or VISUAL environment variables, or 'notepad.exe' on @@ -574,8 +505,6 @@ Windows, or 'vim' on Unix systems</li> <li>Type: String</li> </ul> <p>The command to run for <code>npm edit</code> and <code>npm config edit</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="engine-strict"><code>engine-strict</code></h4> <ul> <li>Default: false</li> @@ -585,8 +514,6 @@ Windows, or 'vim' on Unix systems</li> installing) any package that claims to not be compatible with the current Node.js version.</p> <p>This can be overridden by setting the <code>--force</code> flag.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="fetch-retries"><code>fetch-retries</code></h4> <ul> <li>Default: 2</li> @@ -596,16 +523,12 @@ Node.js version.</p> from the registry.</p> <p>npm will retry idempotent read requests to the registry in the case of network failures or 5xx HTTP errors.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="fetch-retry-factor"><code>fetch-retry-factor</code></h4> <ul> <li>Default: 10</li> <li>Type: Number</li> </ul> <p>The "factor" config for the <code>retry</code> module to use when fetching packages.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="fetch-retry-maxtimeout"><code>fetch-retry-maxtimeout</code></h4> <ul> <li>Default: 60000 (1 minute)</li> @@ -613,8 +536,6 @@ network failures or 5xx HTTP errors.</p> </ul> <p>The "maxTimeout" config for the <code>retry</code> module to use when fetching packages.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="fetch-retry-mintimeout"><code>fetch-retry-mintimeout</code></h4> <ul> <li>Default: 10000 (10 seconds)</li> @@ -622,16 +543,12 @@ packages.</p> </ul> <p>The "minTimeout" config for the <code>retry</code> module to use when fetching packages.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="fetch-timeout"><code>fetch-timeout</code></h4> <ul> <li>Default: 300000 (5 minutes)</li> <li>Type: Number</li> </ul> <p>The maximum amount of time to wait for HTTP requests to complete.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="force"><code>force</code></h4> <ul> <li>Default: false</li> @@ -657,8 +574,6 @@ range (including SemVer-major changes).</li> </ul> <p>If you don't have a clear idea of what you want to do, it is strongly recommended that you do not use this option!</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="foreground-scripts"><code>foreground-scripts</code></h4> <ul> <li>Default: false</li> @@ -669,8 +584,6 @@ scripts for installed packages in the foreground process, sharing standard input, output, and error with the main npm process.</p> <p>Note that this will generally make installs run slower, and be much noisier, but can be useful for debugging.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="format-package-lock"><code>format-package-lock</code></h4> <ul> <li>Default: true</li> @@ -678,8 +591,6 @@ but can be useful for debugging.</p> </ul> <p>Format <code>package-lock.json</code> or <code>npm-shrinkwrap.json</code> as a human readable file.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="fund"><code>fund</code></h4> <ul> <li>Default: true</li> @@ -687,8 +598,6 @@ file.</p> </ul> <p>When "true" displays the message at the end of each <code>npm install</code> acknowledging the number of dependencies looking for funding. See <a href="../commands/npm-fund.html"><code>npm fund</code></a> for details.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="git"><code>git</code></h4> <ul> <li>Default: "git"</li> @@ -696,8 +605,6 @@ acknowledging the number of dependencies looking for funding. See <a href="../co </ul> <p>The command to use for git commands. If git is installed on the computer, but is not in the <code>PATH</code>, then set this to the full path to the git binary.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="git-tag-version"><code>git-tag-version</code></h4> <ul> <li>Default: true</li> @@ -705,8 +612,6 @@ but is not in the <code>PATH</code>, then set this to the full path to the git b </ul> <p>Tag the commit when using the <code>npm version</code> command. Setting this to false results in no commit being made at all.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="global"><code>global</code></h4> <ul> <li>Default: false</li> @@ -721,8 +626,6 @@ of the current working directory.</li> <li>bin files are linked to <code>{prefix}/bin</code></li> <li>man pages are linked to <code>{prefix}/share/man</code></li> </ul> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="global-style"><code>global-style</code></h4> <ul> <li>Default: false</li> @@ -734,8 +637,6 @@ direct dependencies will show in <code>node_modules</code> and everything they d on will be flattened in their <code>node_modules</code> folders. This obviously will eliminate some deduping. If used with <code>legacy-bundling</code>, <code>legacy-bundling</code> will be preferred.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="globalconfig"><code>globalconfig</code></h4> <ul> <li>Default: The global --prefix setting plus 'etc/npmrc'. For example, @@ -743,16 +644,12 @@ will be preferred.</p> <li>Type: Path</li> </ul> <p>The config file to read for global config options.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="heading"><code>heading</code></h4> <ul> <li>Default: "npm"</li> <li>Type: String</li> </ul> <p>The string that starts all the debugging log output.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="https-proxy"><code>https-proxy</code></h4> <ul> <li>Default: null</li> @@ -762,8 +659,6 @@ will be preferred.</p> <code>https_proxy</code> or <code>HTTP_PROXY</code> or <code>http_proxy</code> environment variables are set, proxy settings will be honored by the underlying <code>make-fetch-happen</code> library.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="if-present"><code>if-present</code></h4> <ul> <li>Default: false</li> @@ -776,8 +671,6 @@ it's present and fail if the script fails. This is useful, for example, when running scripts that may only apply for some builds in an otherwise generic CI setup.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="ignore-scripts"><code>ignore-scripts</code></h4> <ul> <li>Default: false</li> @@ -788,8 +681,6 @@ CI setup.</p> <code>npm start</code>, <code>npm stop</code>, <code>npm restart</code>, <code>npm test</code>, and <code>npm run-script</code> will still run their intended script if <code>ignore-scripts</code> is set, but they will <em>not</em> run any pre- or post-scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include"><code>include</code></h4> <ul> <li>Default:</li> @@ -799,8 +690,6 @@ will <em>not</em> run any pre- or post-scripts.</p> <p>This is the inverse of <code>--omit=<type></code>.</p> <p>Dependency types specified in <code>--include</code> will not be omitted, regardless of the order in which omit/include are specified on the command-line.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-staged"><code>include-staged</code></h4> <ul> <li>Default: false</li> @@ -809,8 +698,6 @@ the order in which omit/include are specified on the command-line.</p> <p>Allow installing "staged" published packages, as defined by <a href="https://github.com/npm/rfcs/pull/92">npm RFC PR #92</a>.</p> <p>This is experimental, and not implemented by the npm public registry.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="include-workspace-root"><code>include-workspace-root</code></h4> <ul> <li>Default: false</li> @@ -821,24 +708,18 @@ the order in which omit/include are specified on the command-line.</p> all workspaces via the <code>workspaces</code> flag, will cause npm to operate only on the specified workspaces, and not on the root project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="init-author-email"><code>init-author-email</code></h4> <ul> <li>Default: ""</li> <li>Type: String</li> </ul> <p>The value <code>npm init</code> should use by default for the package author's email.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="init-author-name"><code>init-author-name</code></h4> <ul> <li>Default: ""</li> <li>Type: String</li> </ul> <p>The value <code>npm init</code> should use by default for the package author's name.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="init-author-url"><code>init-author-url</code></h4> <ul> <li>Default: ""</li> @@ -846,16 +727,12 @@ the specified workspaces, and not on the root project.</p> </ul> <p>The value <code>npm init</code> should use by default for the package author's homepage.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="init-license"><code>init-license</code></h4> <ul> <li>Default: "ISC"</li> <li>Type: String</li> </ul> <p>The value <code>npm init</code> should use by default for the package license.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="init-module"><code>init-module</code></h4> <ul> <li>Default: "~/.npm-init.js"</li> @@ -865,8 +742,6 @@ homepage.</p> documentation for the <a href="https://github.com/npm/init-package-json">init-package-json</a> module for more information, or <a href="../commands/npm-init.html">npm init</a>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="init-version"><code>init-version</code></h4> <ul> <li>Default: "1.0.0"</li> @@ -874,8 +749,6 @@ more information, or <a href="../commands/npm-init.html">npm init</a>.</p> </ul> <p>The value that <code>npm init</code> should use by default for the package version number, if not already set in package.json.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="install-links"><code>install-links</code></h4> <ul> <li>Default: false</li> @@ -884,8 +757,6 @@ number, if not already set in package.json.</p> <p>When set file: protocol dependencies that exist outside of the project root will be packed and installed as regular dependencies instead of creating a symlink. This option has no effect on workspaces.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="json"><code>json</code></h4> <ul> <li>Default: false</li> @@ -897,8 +768,6 @@ symlink. This option has no effect on workspaces.</p> saving them to your <code>package.json</code>.</li> </ul> <p>Not supported by all npm commands.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="key"><code>key</code></h4> <ul> <li>Default: null</li> @@ -910,8 +779,6 @@ format with newlines replaced by the string "\n". For example:</p> </code></pre> <p>It is <em>not</em> the path to a key file, though you can set a registry-scoped "keyfile" path like "//other-registry.tld/:keyfile=/path/to/key.pem".</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="legacy-bundling"><code>legacy-bundling</code></h4> <ul> <li>Default: false</li> @@ -921,8 +788,6 @@ format with newlines replaced by the string "\n". For example:</p> such as the one included with node 0.8, can install the package. This eliminates all automatic deduping. If used with <code>global-style</code> this option will be preferred.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="legacy-peer-deps"><code>legacy-peer-deps</code></h4> <ul> <li>Default: false</li> @@ -937,16 +802,12 @@ that collide, it provides a way to move forward resolving the situation.</p> <code>peerDependencies</code> <em>could</em> be unpacked in a correct place.</p> <p>Use of <code>legacy-peer-deps</code> is not recommended, as it will not enforce the <code>peerDependencies</code> contract that meta-dependencies may rely on.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="link"><code>link</code></h4> <ul> <li>Default: false</li> <li>Type: Boolean</li> </ul> <p>Used with <code>npm ls</code>, limiting output to only those packages that are linked.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="local-address"><code>local-address</code></h4> <ul> <li>Default: null</li> @@ -954,8 +815,6 @@ that collide, it provides a way to move forward resolving the situation.</p> </ul> <p>The IP address of the local interface to use when making connections to the npm registry. Must be IPv4 in versions of Node prior to 0.12.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="location"><code>location</code></h4> <ul> <li>Default: "user" unless <code>--global</code> is passed, which will also set this value @@ -972,8 +831,6 @@ of the current working directory.</li> <li>bin files are linked to <code>{prefix}/bin</code></li> <li>man pages are linked to <code>{prefix}/share/man</code></li> </ul> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="lockfile-version"><code>lockfile-version</code></h4> <ul> <li>Default: Version 2 if no lockfile or current lockfile version less than or @@ -992,8 +849,6 @@ and interoperability, at the expense of more bytes on disk.</p> <p>3: Only the new lockfile information introduced in npm version 7. Smaller on disk than lockfile version 2, but not interoperable with older npm versions. Ideal if all users are on npm version 7 and higher.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="loglevel"><code>loglevel</code></h4> <ul> <li>Default: "notice"</li> @@ -1005,8 +860,6 @@ path to that file printed if the execution of a command fails.</p> <p>Any logs of a higher level than the setting are shown. The default is "notice".</p> <p>See also the <code>foreground-scripts</code> config.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="logs-dir"><code>logs-dir</code></h4> <ul> <li>Default: A directory named <code>_logs</code> inside the cache</li> @@ -1014,8 +867,6 @@ path to that file printed if the execution of a command fails.</p> </ul> <p>The location of npm's log directory. See <a href="../using-npm/logging.html"><code>npm logging</code></a> for more information.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="logs-max"><code>logs-max</code></h4> <ul> <li>Default: 10</li> @@ -1023,16 +874,12 @@ for more information.</p> </ul> <p>The maximum number of log files to store.</p> <p>If set to 0, no log files will be written for the current run.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="long"><code>long</code></h4> <ul> <li>Default: false</li> <li>Type: Boolean</li> </ul> <p>Show extended information in <code>ls</code>, <code>search</code>, and <code>help-search</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="maxsockets"><code>maxsockets</code></h4> <ul> <li>Default: 15</li> @@ -1040,8 +887,6 @@ for more information.</p> </ul> <p>The maximum number of connections to use per origin (protocol/host/port combination).</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="message"><code>message</code></h4> <ul> <li>Default: "%s"</li> @@ -1049,8 +894,6 @@ combination).</p> </ul> <p>Commit message which is used by <code>npm version</code> when creating version commit.</p> <p>Any "%s" in the message will be replaced with the version number.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="node-options"><code>node-options</code></h4> <ul> <li>Default: null</li> @@ -1059,16 +902,12 @@ combination).</p> <p>Options to pass through to Node.js via the <code>NODE_OPTIONS</code> environment variable. This does not impact how npm itself is executed but it does impact how lifecycle scripts are called.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="node-version"><code>node-version</code></h4> <ul> <li>Default: Node.js <code>process.version</code> value</li> <li>Type: SemVer string</li> </ul> <p>The node version to use when checking a package's <code>engines</code> setting.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="noproxy"><code>noproxy</code></h4> <ul> <li>Default: The value of the NO_PROXY environment variable</li> @@ -1076,16 +915,12 @@ how lifecycle scripts are called.</p> </ul> <p>Domain extensions that should bypass any proxies.</p> <p>Also accepts a comma-delimited string.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="npm-version"><code>npm-version</code></h4> <ul> <li>Default: Output of <code>npm --version</code></li> <li>Type: SemVer string</li> </ul> <p>The npm version to use when checking a package's <code>engines</code> setting.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="offline"><code>offline</code></h4> <ul> <li>Default: false</li> @@ -1093,8 +928,6 @@ how lifecycle scripts are called.</p> </ul> <p>Force offline mode: no network requests will be done during install. To allow the CLI to fill in missing cache data, see <code>--prefer-offline</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="omit"><code>omit</code></h4> <ul> <li>Default: 'dev' if the <code>NODE_ENV</code> environment variable is set to @@ -1109,8 +942,6 @@ physically installed on disk.</p> it will be included.</p> <p>If the resulting omit list includes <code>'dev'</code>, then the <code>NODE_ENV</code> environment variable will be set to <code>'production'</code> for all lifecycle scripts.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="omit-lockfile-registry-resolved"><code>omit-lockfile-registry-resolved</code></h4> <ul> <li>Default: false</li> @@ -1120,8 +951,6 @@ variable will be set to <code>'production'</code> for all lifecycle scripts.</p> registry dependencies. Subsequent installs will need to resolve tarball endpoints with the configured registry, likely resulting in a longer install time.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="otp"><code>otp</code></h4> <ul> <li>Default: null</li> @@ -1131,24 +960,18 @@ time.</p> when publishing or changing package permissions with <code>npm access</code>.</p> <p>If not set, and a registry response fails with a challenge for a one-time password, npm will prompt on the command line for one.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="pack-destination"><code>pack-destination</code></h4> <ul> <li>Default: "."</li> <li>Type: String</li> </ul> <p>Directory in which <code>npm pack</code> will save tarballs.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="package"><code>package</code></h4> <ul> <li>Default:</li> <li>Type: String (can be set multiple times)</li> </ul> <p>The package or packages to install for <a href="../commands/npm-exec.html"><code>npm exec</code></a></p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="package-lock"><code>package-lock</code></h4> <ul> <li>Default: true</li> @@ -1157,8 +980,6 @@ password, npm will prompt on the command line for one.</p> <p>If set to false, then ignore <code>package-lock.json</code> files when installing. This will also prevent <em>writing</em> <code>package-lock.json</code> if <code>save</code> is true.</p> <p>This configuration does not affect <code>npm ci</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="package-lock-only"><code>package-lock-only</code></h4> <ul> <li>Default: false</li> @@ -1170,8 +991,6 @@ ignoring <code>node_modules</code>.</p> instead of checking <code>node_modules</code> and downloading dependencies.</p> <p>For <code>list</code> this means the output will be based on the tree described by the <code>package-lock.json</code>, rather than the contents of <code>node_modules</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="parseable"><code>parseable</code></h4> <ul> <li>Default: false</li> @@ -1179,8 +998,6 @@ instead of checking <code>node_modules</code> and downloading dependencies.</p> </ul> <p>Output parseable results from commands that write to standard output. For <code>npm search</code>, this will be tab-separated table format.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="prefer-offline"><code>prefer-offline</code></h4> <ul> <li>Default: false</li> @@ -1189,8 +1006,6 @@ instead of checking <code>node_modules</code> and downloading dependencies.</p> <p>If true, staleness checks for cached data will be bypassed, but missing data will be requested from the server. To force full offline mode, use <code>--offline</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="prefer-online"><code>prefer-online</code></h4> <ul> <li>Default: false</li> @@ -1198,8 +1013,6 @@ will be requested from the server. To force full offline mode, use </ul> <p>If true, staleness checks for cached data will be forced, making the CLI look for updates immediately even for fresh package data.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="prefix"><code>prefix</code></h4> <ul> <li>Default: In global mode, the folder where the node executable is installed. @@ -1209,8 +1022,6 @@ file or a node_modules folder.</li> </ul> <p>The location to install global items. If set on the command line, then it forces non-global commands to run in the specified folder.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="preid"><code>preid</code></h4> <ul> <li>Default: ""</li> @@ -1218,8 +1029,6 @@ forces non-global commands to run in the specified folder.</p> </ul> <p>The "prerelease identifier" to use as a prefix for the "prerelease" part of a semver. Like the <code>rc</code> in <code>1.2.0-rc.8</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="progress"><code>progress</code></h4> <ul> <li>Default: <code>true</code> unless running in a known CI system</li> @@ -1228,8 +1037,6 @@ a semver. Like the <code>rc</code> in <code>1.2.0-rc.8</code>.</p> <p>When set to <code>true</code>, npm will display a progress bar during time intensive operations, if <code>process.stderr</code> is a TTY.</p> <p>Set to <code>false</code> to suppress the progress bar.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="proxy"><code>proxy</code></h4> <ul> <li>Default: null</li> @@ -1238,8 +1045,6 @@ operations, if <code>process.stderr</code> is a TTY.</p> <p>A proxy to use for outgoing http requests. If the <code>HTTP_PROXY</code> or <code>http_proxy</code> environment variables are set, proxy settings will be honored by the underlying <code>request</code> library.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="read-only"><code>read-only</code></h4> <ul> <li>Default: false</li> @@ -1247,24 +1052,18 @@ by the underlying <code>request</code> library.</p> </ul> <p>This is used to mark a token as unable to publish when configuring limited access tokens with the <code>npm token create</code> command.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="rebuild-bundle"><code>rebuild-bundle</code></h4> <ul> <li>Default: true</li> <li>Type: Boolean</li> </ul> <p>Rebuild bundled dependencies after installation.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="registry"><code>registry</code></h4> <ul> <li>Default: "<a href="https://registry.npmjs.org/">https://registry.npmjs.org/</a>"</li> <li>Type: URL</li> </ul> <p>The base URL of the npm registry.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="replace-registry-host"><code>replace-registry-host</code></h4> <ul> <li>Default: "npmjs"</li> @@ -1277,8 +1076,6 @@ registry (<a href="https://registry.npmjs.org">https://registry.npmjs.org</a>) t "never", then use the registry value. If set to "always", then replace the registry host with the configured host every time.</p> <p>You may also specify a bare hostname (e.g., "registry.npmjs.org").</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="save"><code>save</code></h4> <ul> <li>Default: <code>true</code> unless when using <code>npm update</code> where it defaults to <code>false</code></li> @@ -1288,8 +1085,6 @@ registry host with the configured host every time.</p> <p>When used with the <code>npm rm</code> command, removes the dependency from <code>package.json</code>.</p> <p>Will also prevent writing to <code>package-lock.json</code> if set to <code>false</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="save-bundle"><code>save-bundle</code></h4> <ul> <li>Default: false</li> @@ -1299,16 +1094,12 @@ registry host with the configured host every time.</p> <code>--save-dev</code>, or <code>--save-optional</code>, then also put it in the <code>bundleDependencies</code> list.</p> <p>Ignored if <code>--save-peer</code> is set, since peerDependencies cannot be bundled.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="save-dev"><code>save-dev</code></h4> <ul> <li>Default: false</li> <li>Type: Boolean</li> </ul> <p>Save installed packages to a package.json file as <code>devDependencies</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="save-exact"><code>save-exact</code></h4> <ul> <li>Default: false</li> @@ -1316,24 +1107,18 @@ registry host with the configured host every time.</p> </ul> <p>Dependencies saved to package.json will be configured with an exact version rather than using npm's default semver range operator.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="save-optional"><code>save-optional</code></h4> <ul> <li>Default: false</li> <li>Type: Boolean</li> </ul> <p>Save installed packages to a package.json file as <code>optionalDependencies</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="save-peer"><code>save-peer</code></h4> <ul> <li>Default: false</li> <li>Type: Boolean</li> </ul> <p>Save installed packages to a package.json file as <code>peerDependencies</code></p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="save-prefix"><code>save-prefix</code></h4> <ul> <li>Default: "^"</li> @@ -1344,8 +1129,6 @@ rather than using npm's default semver range operator.</p> <p>For example if a package has version <code>1.2.3</code>, by default its version is set to <code>^1.2.3</code> which allows minor upgrades for that package, but after <code>npm config set save-prefix='~'</code> it would be set to <code>~1.2.3</code> which only allows patch upgrades.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="save-prod"><code>save-prod</code></h4> <ul> <li>Default: false</li> @@ -1356,8 +1139,6 @@ a package already exists in <code>devDependencies</code> or <code>optionalDepend you want to move it to be a non-optional production dependency.</p> <p>This is the default behavior if <code>--save</code> is true, and neither <code>--save-dev</code> or <code>--save-optional</code> are true.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="scope"><code>scope</code></h4> <ul> <li>Default: the scope of the current project, if any, or ""</li> @@ -1379,24 +1160,18 @@ installation of packages specified according to the pattern # instead of just named "whatever" npm init --scope=@foo --yes </code></pre> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="script-shell"><code>script-shell</code></h4> <ul> <li>Default: '/bin/sh' on POSIX systems, 'cmd.exe' on Windows</li> <li>Type: null or String</li> </ul> <p>The shell to use for scripts run with the <code>npm exec</code>, <code>npm run</code> and <code>npm init <package-spec></code> commands.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="searchexclude"><code>searchexclude</code></h4> <ul> <li>Default: ""</li> <li>Type: String</li> </ul> <p>Space-separated options that limit the results from search.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="searchlimit"><code>searchlimit</code></h4> <ul> <li>Default: 20</li> @@ -1404,16 +1179,12 @@ npm init --scope=@foo --yes </ul> <p>Number of items to limit search results to. Will not apply at all to legacy searches.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="searchopts"><code>searchopts</code></h4> <ul> <li>Default: ""</li> <li>Type: String</li> </ul> <p>Space-separated options that are always passed to search.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="searchstaleness"><code>searchstaleness</code></h4> <ul> <li>Default: 900</li> @@ -1421,8 +1192,6 @@ searches.</p> </ul> <p>The age of the cache, in seconds, before another registry request is made if using legacy search endpoint.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="shell"><code>shell</code></h4> <ul> <li>Default: SHELL environment variable, or "bash" on Posix, or "cmd.exe" on @@ -1430,8 +1199,6 @@ Windows</li> <li>Type: String</li> </ul> <p>The shell to run for the <code>npm explore</code> command.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="sign-git-commit"><code>sign-git-commit</code></h4> <ul> <li>Default: false</li> @@ -1441,8 +1208,6 @@ Windows</li> version using <code>-S</code> to add a signature.</p> <p>Note that git requires you to have set up GPG keys in your git configs for this to work properly.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="sign-git-tag"><code>sign-git-tag</code></h4> <ul> <li>Default: false</li> @@ -1452,8 +1217,6 @@ this to work properly.</p> <code>-s</code> to add a signature.</p> <p>Note that git requires you to have set up GPG keys in your git configs for this to work properly.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="strict-peer-deps"><code>strict-peer-deps</code></h4> <ul> <li>Default: false</li> @@ -1470,8 +1233,6 @@ the range set in their package's <code>peerDependencies</code> object.</p> <p>When such and override is performed, a warning is printed, explaining the conflict and the packages involved. If <code>--strict-peer-deps</code> is set, then this warning is treated as a failure.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="strict-ssl"><code>strict-ssl</code></h4> <ul> <li>Default: true</li> @@ -1480,8 +1241,6 @@ this warning is treated as a failure.</p> <p>Whether or not to do SSL key validation when making requests to the registry via https.</p> <p>See also the <code>ca</code> config.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="tag"><code>tag</code></h4> <ul> <li>Default: "latest"</li> @@ -1493,8 +1252,6 @@ then it will install the specified tag.</p> command, if no explicit tag is given.</p> <p>When used by the <code>npm diff</code> command, this is the tag used to fetch the tarball that will be compared with the local files by default.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="tag-version-prefix"><code>tag-version-prefix</code></h4> <ul> <li>Default: "v"</li> @@ -1506,8 +1263,6 @@ it to the empty string: <code>""</code>.</p> <p>Because other tools may rely on the convention that npm version tags look like <code>v1.0.0</code>, <em>only use this property if it is absolutely necessary</em>. In particular, use care when overriding this setting for public packages.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="timing"><code>timing</code></h4> <ul> <li>Default: false</li> @@ -1518,8 +1273,6 @@ particular, use care when overriding this setting for public packages.</p> <code>_timing.json</code> is a newline delimited list of JSON objects.</p> <p>You can quickly view it with this <a href="https://npm.im/json">json</a> command line: <code>npm exec -- json -g < ~/.npm/_timing.json</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="umask"><code>umask</code></h4> <ul> <li>Default: 0</li> @@ -1536,8 +1289,6 @@ rather adds the <code>--umask</code> config to it.</p> <p>Thus, the effective default umask value on most POSIX systems is 0o22, meaning that folders and executables are created with a mode of 0o755 and other files are created with a mode of 0o644.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="unicode"><code>unicode</code></h4> <ul> <li>Default: false on windows, true on mac/unix systems with a unicode locale, @@ -1546,8 +1297,6 @@ as defined by the <code>LC_ALL</code>, <code>LC_CTYPE</code>, or <code>LANG</cod </ul> <p>When set to true, npm uses unicode characters in the tree output. When false, it uses ascii characters instead of unicode glyphs.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="update-notifier"><code>update-notifier</code></h4> <ul> <li>Default: true</li> @@ -1555,16 +1304,12 @@ false, it uses ascii characters instead of unicode glyphs.</p> </ul> <p>Set to false to suppress the update notification when using an older version of npm than the latest.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="usage"><code>usage</code></h4> <ul> <li>Default: false</li> <li>Type: Boolean</li> </ul> <p>Show short usage output about the command specified.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="user-agent"><code>user-agent</code></h4> <ul> <li>Default: "npm/{npm-version} node/{node-version} {platform} {arch} @@ -1583,8 +1328,6 @@ are set.</li> <li><code>{ci}</code> - The value of the <code>ci-name</code> config, if set, prefixed with <code>ci/</code>, or an empty string if <code>ci-name</code> is empty.</li> </ul> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="userconfig"><code>userconfig</code></h4> <ul> <li>Default: "~/.npmrc"</li> @@ -1594,8 +1337,6 @@ an empty string if <code>ci-name</code> is empty.</li> <p>This may be overridden by the <code>npm_config_userconfig</code> environment variable or the <code>--userconfig</code> command line option, but may <em>not</em> be overridden by settings in the <code>globalconfig</code> file.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="version"><code>version</code></h4> <ul> <li>Default: false</li> @@ -1603,8 +1344,6 @@ settings in the <code>globalconfig</code> file.</p> </ul> <p>If true, output the npm version and exit successfully.</p> <p>Only relevant when specified explicitly on the command line.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="versions"><code>versions</code></h4> <ul> <li>Default: false</li> @@ -1614,8 +1353,6 @@ settings in the <code>globalconfig</code> file.</p> the version in the current working directory's <code>package.json</code> file if one exists, and exit successfully.</p> <p>Only relevant when specified explicitly on the command line.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="viewer"><code>viewer</code></h4> <ul> <li>Default: "man" on Posix, "browser" on Windows</li> @@ -1623,16 +1360,12 @@ exists, and exit successfully.</p> </ul> <p>The program to use to view help content.</p> <p>Set to <code>"browser"</code> to view html help content in the default web browser.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="which"><code>which</code></h4> <ul> <li>Default: null</li> <li>Type: null or Number</li> </ul> <p>If there are multiple funding sources, which 1-indexed source URL to open.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspace"><code>workspace</code></h4> <ul> <li>Default:</li> @@ -1652,8 +1385,6 @@ workspaces within that folder)</li> workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project.</p> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces"><code>workspaces</code></h4> <ul> <li>Default: null</li> @@ -1670,8 +1401,6 @@ other things (test, exec, publish, etc.) will operate on the root project, <em>unless</em> one or more workspaces are specified in the <code>workspace</code> config.</li> </ul> <p>This value is not exported to the environment for child processes.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="workspaces-update"><code>workspaces-update</code></h4> <ul> <li>Default: true</li> @@ -1679,8 +1408,6 @@ other things (test, exec, publish, etc.) will operate on the root project, </ul> <p>If set to true, the npm cli will run an update after operations that may possibly change the workspaces installed to the <code>node_modules</code> folder.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="yes"><code>yes</code></h4> <ul> <li>Default: null</li> @@ -1688,8 +1415,6 @@ possibly change the workspaces installed to the <code>node_modules</code> folder </ul> <p>Automatically answer "yes" to any prompts that npm might print on the command line.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="also"><code>also</code></h4> <ul> <li>Default: null</li> @@ -1697,8 +1422,6 @@ command line.</p> <li>DEPRECATED: Please use --include=dev instead.</li> </ul> <p>When set to <code>dev</code> or <code>development</code>, this is an alias for <code>--include=dev</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="cache-max"><code>cache-max</code></h4> <ul> <li>Default: Infinity</li> @@ -1706,8 +1429,6 @@ command line.</p> <li>DEPRECATED: This option has been deprecated in favor of <code>--prefer-online</code></li> </ul> <p><code>--cache-max=0</code> is an alias for <code>--prefer-online</code></p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="cache-min"><code>cache-min</code></h4> <ul> <li>Default: 0</li> @@ -1715,8 +1436,6 @@ command line.</p> <li>DEPRECATED: This option has been deprecated in favor of <code>--prefer-offline</code>.</li> </ul> <p><code>--cache-min=9999 (or bigger)</code> is an alias for <code>--prefer-offline</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="dev"><code>dev</code></h4> <ul> <li>Default: false</li> @@ -1724,8 +1443,6 @@ command line.</p> <li>DEPRECATED: Please use --include=dev instead.</li> </ul> <p>Alias for <code>--include=dev</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="initauthoremail"><code>init.author.email</code></h4> <ul> <li>Default: ""</li> @@ -1733,8 +1450,6 @@ command line.</p> <li>DEPRECATED: Use <code>--init-author-email</code> instead.</li> </ul> <p>Alias for <code>--init-author-email</code></p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="initauthorname"><code>init.author.name</code></h4> <ul> <li>Default: ""</li> @@ -1742,8 +1457,6 @@ command line.</p> <li>DEPRECATED: Use <code>--init-author-name</code> instead.</li> </ul> <p>Alias for <code>--init-author-name</code></p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="initauthorurl"><code>init.author.url</code></h4> <ul> <li>Default: ""</li> @@ -1751,8 +1464,6 @@ command line.</p> <li>DEPRECATED: Use <code>--init-author-url</code> instead.</li> </ul> <p>Alias for <code>--init-author-url</code></p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="initlicense"><code>init.license</code></h4> <ul> <li>Default: "ISC"</li> @@ -1760,8 +1471,6 @@ command line.</p> <li>DEPRECATED: Use <code>--init-license</code> instead.</li> </ul> <p>Alias for <code>--init-license</code></p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="initmodule"><code>init.module</code></h4> <ul> <li>Default: "~/.npm-init.js"</li> @@ -1769,8 +1478,6 @@ command line.</p> <li>DEPRECATED: Use <code>--init-module</code> instead.</li> </ul> <p>Alias for <code>--init-module</code></p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="initversion"><code>init.version</code></h4> <ul> <li>Default: "1.0.0"</li> @@ -1778,8 +1485,6 @@ command line.</p> <li>DEPRECATED: Use <code>--init-version</code> instead.</li> </ul> <p>Alias for <code>--init-version</code></p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="only"><code>only</code></h4> <ul> <li>Default: null</li> @@ -1787,8 +1492,6 @@ command line.</p> <li>DEPRECATED: Use <code>--omit=dev</code> to omit dev dependencies from the install.</li> </ul> <p>When set to <code>prod</code> or <code>production</code>, this is an alias for <code>--omit=dev</code>.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="optional"><code>optional</code></h4> <ul> <li>Default: null</li> @@ -1798,8 +1501,6 @@ command line.</p> </ul> <p>Default value does install optional deps unless otherwise omitted.</p> <p>Alias for --include=optional or --omit=optional</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="production"><code>production</code></h4> <ul> <li>Default: null</li> @@ -1807,8 +1508,6 @@ command line.</p> <li>DEPRECATED: Use <code>--omit=dev</code> instead.</li> </ul> <p>Alias for <code>--omit=dev</code></p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="shrinkwrap"><code>shrinkwrap</code></h4> <ul> <li>Default: true</li> @@ -1816,8 +1515,6 @@ command line.</p> <li>DEPRECATED: Use the --package-lock setting instead.</li> </ul> <p>Alias for --package-lock</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="sso-poll-frequency"><code>sso-poll-frequency</code></h4> <ul> <li>Default: 500</li> @@ -1827,8 +1524,6 @@ future version of npm in favor of web-based login.</li> </ul> <p>When used with SSO-enabled <code>auth-type</code>s, configures how regularly the registry should be polled while the user is completing authentication.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="sso-type"><code>sso-type</code></h4> <ul> <li>Default: "oauth"</li> @@ -1837,8 +1532,6 @@ registry should be polled while the user is completing authentication.</p> future version of npm in favor of web-based login.</li> </ul> <p>If <code>--auth-type=sso</code>, the type of SSO type to use.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h4 id="tmp"><code>tmp</code></h4> <ul> <li>Default: The value returned by the Node.js <code>os.tmpdir()</code> method @@ -1850,9 +1543,6 @@ special location in the cache, and they are managed by </ul> <p>Historically, the location where temporary files were stored. No longer relevant.</p> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> -<!-- raw HTML omitted --> <h3 id="see-also">See also</h3> <ul> <li><a href="../commands/npm-config.html">npm config</a></li> |