diff options
Diffstat (limited to 'deps/npm/docs/content/cli-commands')
59 files changed, 206 insertions, 198 deletions
diff --git a/deps/npm/docs/content/cli-commands/npm-access.md b/deps/npm/docs/content/cli-commands/npm-access.md index 370ea5fa3b..0fbce9c075 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-access.md +++ b/deps/npm/docs/content/cli-commands/npm-access.md @@ -4,7 +4,7 @@ title: npm-access description: Set access level on published packages --- -# npm-access +# npm-access(1) ## Set access level on published packages diff --git a/deps/npm/docs/content/cli-commands/npm-adduser.md b/deps/npm/docs/content/cli-commands/npm-adduser.md index 0eaf63c408..2df35e45fc 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-adduser.md +++ b/deps/npm/docs/content/cli-commands/npm-adduser.md @@ -4,7 +4,7 @@ title: npm-adduser description: Set access level on published packages --- -# npm-adduser +# npm-adduser(1) ## Add a registry user account @@ -20,7 +20,7 @@ aliases: login, add-user Create or verify a user named `<username>` in the specified registry, and save the credentials to the `.npmrc` file. If no registry is specified, -the default registry will be used (see [`npm-config`](npm-config)). +the default registry will be used (see [`config`](/using-npm/config)). The username, password, and email are read in from prompts. @@ -43,19 +43,19 @@ Default: https://registry.npmjs.org/ The base URL of the npm package registry. If `scope` is also specified, this registry will only be used for packages with that scope. `scope` defaults -to the scope of the project directory you're currently in, if any. See [`npm-scope`](/docs/using-npm/scope). +to the scope of the project directory you're currently in, if any. See [`scope`](/using-npm/scope). #### scope Default: none If specified, the user and login credentials given will be associated -with the specified scope. See [`npm-scope`](/docs/using-npm/scope). You can use both at the same time, +with the specified scope. See [`scope`](/using-npm/scope). You can use both at the same time, e.g. ```bash npm adduser --registry=http://myregistry.example.com --scope=@myco -``` +``` This will set a registry for the given scope and login or create a user for that registry at the same time. @@ -75,9 +75,7 @@ registries. Can be used with `--registry` and / or `--scope`, e.g. This will ensure that all requests to that registry (including for tarballs) include an authorization header. This setting may be necessary for use with private registries where metadata and package tarballs are stored on hosts with -different hostnames. See `always-auth` in [`npm-config`](/docs/using-npm/config) for more details on -always-auth. Registry-specific configuration of `always-auth` takes precedence -over any global configuration. +different hostnames. See `always-auth` in [`config`](/using-npm/config) for more details on always-auth. Registry-specific configuration of `always-auth` takes precedence over any global configuration. #### auth-type diff --git a/deps/npm/docs/content/cli-commands/npm-audit.md b/deps/npm/docs/content/cli-commands/npm-audit.md index bf1b9e5ca3..0aba874f96 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-audit.md +++ b/deps/npm/docs/content/cli-commands/npm-audit.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-audit description: Run a security audit --- -# npm-audit +# npm-audit(1) ## Run a security audit diff --git a/deps/npm/docs/content/cli-commands/npm-bin.md b/deps/npm/docs/content/cli-commands/npm-bin.md index 778b711a1d..6c7ce0eee5 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-bin.md +++ b/deps/npm/docs/content/cli-commands/npm-bin.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-bin description: Display npm bin folder --- -# npm-bin +# npm-bin(1) ## Display npm bin folder diff --git a/deps/npm/docs/content/cli-commands/npm-bugs.md b/deps/npm/docs/content/cli-commands/npm-bugs.md index 59822521d9..dcc9c358df 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-bugs.md +++ b/deps/npm/docs/content/cli-commands/npm-bugs.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-bugs description: Bugs for a package in a web browser maybe --- -# npm-bugs +# npm-bugs(1) ## Bugs for a package in a web browser maybe diff --git a/deps/npm/docs/content/cli-commands/npm-build.md b/deps/npm/docs/content/cli-commands/npm-build.md index bc01e0b3c6..b657129787 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-build.md +++ b/deps/npm/docs/content/cli-commands/npm-build.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-build description: Build a package --- -# npm-build +# npm-build(1) ## Build a package diff --git a/deps/npm/docs/content/cli-commands/npm-bundle.md b/deps/npm/docs/content/cli-commands/npm-bundle.md index a0d4f6dbe8..76417ac8b0 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-bundle.md +++ b/deps/npm/docs/content/cli-commands/npm-bundle.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-bundle description: REMOVED --- -# npm-bundle +# npm-bundle(1) ## REMOVED diff --git a/deps/npm/docs/content/cli-commands/npm-cache.md b/deps/npm/docs/content/cli-commands/npm-cache.md index 35e835a5cd..ed31a32042 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-cache.md +++ b/deps/npm/docs/content/cli-commands/npm-cache.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-cache description: Manipulates packages cache --- -# npm-cache +# npm-cache(1) ## Manipulates packages cache diff --git a/deps/npm/docs/content/cli-commands/npm-ci.md b/deps/npm/docs/content/cli-commands/npm-ci.md index 01b1252402..357ba16cf6 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-ci.md +++ b/deps/npm/docs/content/cli-commands/npm-ci.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-ci description: Install a project with a clean slate --- -# npm-ci +# npm-ci(1) ## Install a project with a clean slate @@ -45,7 +45,7 @@ cache: ### Description -This command is similar to [`npm-install`](npm-install), except it's meant to be used in +This command is similar to [`npm install`](/cli-commands/npm-install), except it's meant to be used in automated environments such as test platforms, continuous integration, and deployment -- or any situation where you want to make sure you're doing a clean install of your dependencies. It can be significantly faster than a regular npm diff --git a/deps/npm/docs/content/cli-commands/npm-completion.md b/deps/npm/docs/content/cli-commands/npm-completion.md index 2331f97581..59bfca503e 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-completion.md +++ b/deps/npm/docs/content/cli-commands/npm-completion.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-completion description: Tab Completion for npm --- -# npm-completion +# npm-completion(1) ## Tab Completion for npm @@ -28,8 +28,8 @@ npm completion >> ~/.zshrc ``` You may of course also pipe the output of `npm completion` to a file -such as `/usr/local/etc/bash_completion.d/npm` or -`/etc/bash_completion.d/npm` if you have a system that will read +such as `/usr/local/etc/bash_completion.d/npm` or +`/etc/bash_completion.d/npm` if you have a system that will read that file for you. When `COMP_CWORD`, `COMP_LINE`, and `COMP_POINT` are defined in the diff --git a/deps/npm/docs/content/cli-commands/npm-config.md b/deps/npm/docs/content/cli-commands/npm-config.md index c4419e19e7..c2f2033b06 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-config.md +++ b/deps/npm/docs/content/cli-commands/npm-config.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-config description: Manage the npm configuration files --- -# npm-config +# npm-config(1) ## Manage the npm configuration files @@ -26,9 +26,9 @@ aliases: c npm gets its config settings from the command line, environment variables, `npmrc` files, and in some cases, the `package.json` file. -See [npmrc](/docs/configuring-npm/npmrc) for more information about the npmrc files. +See [npmrc](/configuring-npm/npmrc) for more information about the npmrc files. -See [config](/docs/using-npm/config) for a more thorough discussion of the mechanisms +See [config](/using-npm/config) for a more thorough discussion of the mechanisms involved. The `npm config` command can be used to update and edit the contents diff --git a/deps/npm/docs/content/cli-commands/npm-dedupe.md b/deps/npm/docs/content/cli-commands/npm-dedupe.md index a153ec7714..e15a12ba7c 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-dedupe.md +++ b/deps/npm/docs/content/cli-commands/npm-dedupe.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-dedupe description: Reduce duplication --- -# npm-dedupe +# npm-dedupe(1) ## Reduce duplication @@ -32,7 +32,7 @@ a `-- c@1.0.10 ``` -In this case, `npm-dedupe` will transform the tree to: +In this case, `npm dedupe` will transform the tree to: ```bash a diff --git a/deps/npm/docs/content/cli-commands/npm-deprecate.md b/deps/npm/docs/content/cli-commands/npm-deprecate.md index 0a038e0255..d2d9613f65 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-deprecate.md +++ b/deps/npm/docs/content/cli-commands/npm-deprecate.md @@ -1,9 +1,9 @@ --- -section: cli-commands +section: cli-commands title: npm-deprecate description: Deprecate a version of a package --- -# npm-deprecate +# npm-deprecate(1) ## Deprecate a version of a package @@ -17,7 +17,7 @@ npm deprecate <pkg>[@<version>] <message> This command will update the npm registry entry for a package, providing a deprecation warning to all who attempt to install it. -It works on [version ranges](https://semver.npmjs.com/) as well as specific +It works on [version ranges](https://semver.npmjs.com/) as well as specific versions, so you can do something like this: ```bash npm deprecate my-thing@"< 0.2.3" "critical bug fixed in v0.2.3" @@ -26,8 +26,8 @@ npm deprecate my-thing@"< 0.2.3" "critical bug fixed in v0.2.3" Note that you must be the package owner to deprecate something. See the `owner` and `adduser` help topics. -To un-deprecate a package, specify an empty string (`""`) for the `message` -argument. Note that you must use double quotes with no space between them to +To un-deprecate a package, specify an empty string (`""`) for the `message` +argument. Note that you must use double quotes with no space between them to format an empty string. ### See Also diff --git a/deps/npm/docs/content/cli-commands/npm-dist-tag.md b/deps/npm/docs/content/cli-commands/npm-dist-tag.md index 5a1c0c0dfc..c7921c7f73 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-dist-tag.md +++ b/deps/npm/docs/content/cli-commands/npm-dist-tag.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-dist-tag description: Modify package distribution tags --- -# npm-dist-tag +# npm-dist-tag(1) ## Modify package distribution tags diff --git a/deps/npm/docs/content/cli-commands/npm-docs.md b/deps/npm/docs/content/cli-commands/npm-docs.md index 0600a7227e..46f5cd0d90 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-docs.md +++ b/deps/npm/docs/content/cli-commands/npm-docs.md @@ -1,14 +1,13 @@ --- -section: cli-commands +section: cli-commands title: npm-docs description: Docs for a package in a web browser maybe --- -# npm-docs +# npm-docs(1) ## Docs for a package in a web browser maybe - ### Synopsis ```bash diff --git a/deps/npm/docs/content/cli-commands/npm-doctor.md b/deps/npm/docs/content/cli-commands/npm-doctor.md index ee94fe35fb..7cec349e5a 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-doctor.md +++ b/deps/npm/docs/content/cli-commands/npm-doctor.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-doctor description: Check your environments --- -# npm-doctor +# npm-doctor(1) ## Check your environments diff --git a/deps/npm/docs/content/cli-commands/npm-edit.md b/deps/npm/docs/content/cli-commands/npm-edit.md index c349e49cbf..94b6a087fa 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-edit.md +++ b/deps/npm/docs/content/cli-commands/npm-edit.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-edit description: Edit an installed package --- -# npm-edit +# npm-edit(1) ## Edit an installed package diff --git a/deps/npm/docs/content/cli-commands/npm-explore.md b/deps/npm/docs/content/cli-commands/npm-explore.md index 0e17bfa7cd..8ded96d409 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-explore.md +++ b/deps/npm/docs/content/cli-commands/npm-explore.md @@ -1,12 +1,12 @@ --- -section: cli-commands +section: cli-commands title: npm-explore description: Browse an installed package --- -# npm-explore +# npm-explore(1) -## description: Browse an installed package +## Browse an installed package ### Synopsis diff --git a/deps/npm/docs/content/cli-commands/npm-fund.md b/deps/npm/docs/content/cli-commands/npm-fund.md index b5cabab5e5..64894e291f 100644 --- a/deps/npm/docs/content/cli-commands/npm-fund.md +++ b/deps/npm/docs/content/cli-commands/npm-fund.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-fund description: Retrieve funding information --- -# npm-fund +# npm-fund(1) ## Retrieve funding information @@ -53,7 +53,8 @@ Set it to `false` in order to use all-ansi output. ## See Also -* [npm-docs](/cli-commands/npm-docs) -* [npm-config](/cli-commands/npm-config) -* [npm-install](/cli-commands/npm-install) -* [npm-ls](/cli-commands/npm-ls) +* [npm docs](/cli-commands/npm-docs) +* [npm config](/cli-commands/npm-config) +* [npm install](/cli-commands/npm-install) +* [npm ls](/cli-commands/npm-ls) + diff --git a/deps/npm/docs/content/cli-commands/npm-help-search.md b/deps/npm/docs/content/cli-commands/npm-help-search.md index b3b863006f..69d005cb16 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-help-search.md +++ b/deps/npm/docs/content/cli-commands/npm-help-search.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-help-search description: Search npm help documentation --- -# npm-help-search +# npm-help-search(1) ## Search npm help documentation diff --git a/deps/npm/docs/content/cli-commands/npm-help.md b/deps/npm/docs/content/cli-commands/npm-help.md index 346a90ba97..c47676ffca 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-help.md +++ b/deps/npm/docs/content/cli-commands/npm-help.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-help description: Get help on npm --- -# npm-help +# npm-help(1) ## Get help on npm diff --git a/deps/npm/docs/content/cli-commands/npm-hook.md b/deps/npm/docs/content/cli-commands/npm-hook.md index b77e0e16f0..ce4bbccb35 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-hook.md +++ b/deps/npm/docs/content/cli-commands/npm-hook.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-hook description: Manage registry hooks --- -# npm-hook +# npm-hook(1) ## Manage registry hooks @@ -56,8 +56,7 @@ $ npm hook rm id-deadbeef ### Description -Allows you to manage [npm -hooks](https://blog.npmjs.org/post/145260155635/introducing-hooks-get-notifications-of-npm), +Allows you to manage [npm hooks](https://blog.npmjs.org/post/145260155635/introducing-hooks-get-notifications-of-npm), including adding, removing, listing, and updating. Hooks allow you to configure URL endpoints that will be notified whenever a diff --git a/deps/npm/docs/content/cli-commands/npm-init.md b/deps/npm/docs/content/cli-commands/npm-init.md index 5e73262046..73ad74b23e 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-init.md +++ b/deps/npm/docs/content/cli-commands/npm-init.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-init description: create a package.json file --- -# npm-init +# npm-init(1) ## create a package.json file diff --git a/deps/npm/docs/content/cli-commands/npm-install-ci-test.md b/deps/npm/docs/content/cli-commands/npm-install-ci-test.md index 0b3d0d4c16..98e40f4b27 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-install-ci-test.md +++ b/deps/npm/docs/content/cli-commands/npm-install-ci-test.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-install-ci-test description: Install a project with a clean slate and run tests --- -# npm install-ci-test +# npm install-ci-test(1) ## Install a project with a clean slate and run tests diff --git a/deps/npm/docs/content/cli-commands/npm-install-test.md b/deps/npm/docs/content/cli-commands/npm-install-test.md index 8521780f52..b86a519911 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-install-test.md +++ b/deps/npm/docs/content/cli-commands/npm-install-test.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-install-test description: Install package(s) and run tests --- -# npm install-test +# npm install-test(1) ## Install package(s) and run tests diff --git a/deps/npm/docs/content/cli-commands/npm-install.md b/deps/npm/docs/content/cli-commands/npm-install.md index 71983aee67..8e661bf643 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-install.md +++ b/deps/npm/docs/content/cli-commands/npm-install.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-install description: Install a package --- -# npm-install +# npm-install(1) ## Install a package @@ -16,6 +16,7 @@ npm install [<@scope>/]<name> npm install [<@scope>/]<name>@<tag> npm install [<@scope>/]<name>@<version> npm install [<@scope>/]<name>@<version range> +npm install <alias>@npm:<name> npm install <git-host>:<git-user>/<repo-name> npm install <git repo url> npm install <tarball file> @@ -31,15 +32,15 @@ common options: [-P|--save-prod|-D|--save-dev|-O|--save-optional] [-E|--save-exa This command installs a package, and any packages that it depends on. If the package has a package-lock or shrinkwrap file, the installation of dependencies will be driven by that, with an `npm-shrinkwrap.json` taking precedence if both -files exist. See [package-lock.json](/docs/configuring-npm/package-lock.json) and [`npm-shrinkwrap`](npm-shrinkwrap). +files exist. See [package-lock.json](/configuring-npm/package-lock-json) and [`npm shrinkwrap`](/cli-commands/npm-shrinkwrap). A `package` is: -* a) a folder containing a program described by a [`package.json`](/docs/configuring-npm/package-json) file +* a) a folder containing a program described by a [`package.json`](/configuring-npm/package-json) file * b) a gzipped tarball containing (a) * c) a url that resolves to (b) -* d) a `<name>@<version>` that is published on the registry (see [`npm-registry`](npm-registry)) with (c) -* e) a `<name>@<tag>` (see [`npm-dist-tag`](npm-dist-tag)) that points to (d) +* d) a `<name>@<version>` that is published on the registry (see [`registry`](/using-npm/registry)) with (c) +* e) a `<name>@<tag>` (see [`npm dist-tag`](/cli-commands/npm-dist-tag)) that points to (d) * f) a `<name>` that has a "latest" tag satisfying (e) * g) a `<git remote url>` that resolves to (a) @@ -58,11 +59,13 @@ after packing it up into a tarball (b). directory) as a global package. By default, `npm install` will install all modules listed as dependencies - in [`package.json`](/docs/configuring-npm/package-json). + in [`package.json`](/configuring-npm/package-json). With the `--production` flag (or when the `NODE_ENV` environment variable is set to `production`), npm will not install modules listed in - `devDependencies`. + `devDependencies`. To install all modules listed in both `dependencies` + and `devDependencies` when `NODE_ENV` environment variable is set to `production`, + you can use `--production=false`. > NOTE: The `--production` flag has no particular meaning when adding a dependency to a project. @@ -102,7 +105,7 @@ after packing it up into a tarball (b). * `npm install [<@scope>/]<name>`: Do a `<name>@<tag>` install, where `<tag>` is the "tag" config. (See - [`npm-config`](/docs/using-npm/config). The config's default value is `latest`.) + [`config`](/using-npm/config). The config's default value is `latest`.) In most cases, this will install the version of the modules tagged as `latest` on the npm registry. @@ -111,6 +114,24 @@ after packing it up into a tarball (b). npm install sax +* `npm install <alias>@npm:<name>`: + + Install a package under a custom alias. Allows multiple versions of + a same-name package side-by-side, more convenient import names for + packages with otherwise long ones and using git forks replacements + or forked npm packages as replacements. Aliasing works only on your + project and does not rename packages in transitive dependencies. + Aliases should follow the naming conventions stated in + [`validate-npm-package-name`](https://www.npmjs.com/package/validate-npm-package-name#naming-rules). + + Examples: + + npm install my-react@npm:react + npm install jquery2@npm:jquery@2 + npm install jquery3@npm:jquery@3 + npm install npa@npm:npm-package-arg + + `npm install` saves any specified packages into `dependencies` by default. Additionally, you can control where and how they get saved with some additional flags: @@ -138,7 +159,7 @@ after packing it up into a tarball (b). `<scope>` is optional. The package will be downloaded from the registry associated with the specified scope. If no registry is associated with - the given scope the default registry is assumed. See [`npm-scope`](/docs/using-npm/scope). + the given scope the default registry is assumed. See [`scope`](/using-npm/scope). Note: if you do not include the @-symbol on your scope name, npm will interpret this as a GitHub repository instead, see below. Scopes names @@ -188,7 +209,7 @@ after packing it up into a tarball (b). * `npm install [<@scope>/]<name>@<version range>`: Install a version of the package matching the specified version range. This - will follow the same rules for resolving dependencies described in [`package.json`](/docs/configuring-npm/package-json). + will follow the same rules for resolving dependencies described in [`package.json`](/configuring-npm/package-json). Note that most version ranges must be put in quotes so that your shell will treat it as a single argument. @@ -266,7 +287,7 @@ after packing it up into a tarball (b). done installing. Examples: - + ```bash npm install mygithubuser/myproject npm install github:mygithubuser/myproject @@ -283,7 +304,7 @@ after packing it up into a tarball (b). done installing. Example: - + ```bash npm install gist:101a11beef ``` @@ -305,7 +326,7 @@ after packing it up into a tarball (b). done installing. Example: - + ```bash npm install bitbucket:mybitbucketuser/myproject ``` @@ -327,7 +348,7 @@ after packing it up into a tarball (b). done installing. Example: - + ```bash npm install gitlab:mygitlabuser/myproject npm install gitlab:myusr/myproj#semver:^5.0 @@ -358,11 +379,11 @@ npm install sax --force ``` The `--no-fund` argument will hide the message displayed at the end of each -install that aknowledges the number of dependencies looking for funding. +install that acknowledges the number of dependencies looking for funding. See `npm-fund(1)` The `-g` or `--global` argument will cause npm to install the package globally -rather than locally. See [npm-folders](/docs/configuring-npm/folders). +rather than locally. See [folders](/configuring-npm/folders). The `--global-style` argument will cause npm to install the package into your local `node_modules` folder with the same layout it uses with the @@ -371,7 +392,7 @@ global `node_modules` folder. Only your direct dependencies will show in `node_modules` folders. This obviously will eliminate some deduping. The `--ignore-scripts` argument will cause npm to not execute any -scripts defined in the package.json. See [`npm-scripts`](/docs/using-npm/scripts). +scripts defined in the package.json. See [`scripts`](/using-npm/scripts). The `--legacy-bundling` argument will cause npm to install the package such that versions of npm prior to 1.4, such as the one included with node 0.8, @@ -402,7 +423,7 @@ The `--only={prod[uction]|dev[elopment]}` argument will cause either only The `--no-audit` argument can be used to disable sending of audit reports to the configured registries. See [`npm-audit`](npm-audit) for details on what is sent. -See [`npm-config`](/docs/using-npm/config). Many of the configuration params have some +See [`config`](/using-npm/config). Many of the configuration params have some effect on installation, since that's most of what npm does. #### Algorithm @@ -450,8 +471,7 @@ privately for itself. This algorithm is deterministic, but different trees may be produced if two dependencies are requested for installation in a different order. -See [npm-folders](/docs/configuring-npm/folders) for a more detailed description of the specific -folder structures that npm creates. +See [folders](/configuring-npm/folders) for a more detailed description of the specific folder structures that npm creates. ### Limitations of npm's Install Algorithm diff --git a/deps/npm/docs/content/cli-commands/npm-link.md b/deps/npm/docs/content/cli-commands/npm-link.md index ef997557b1..5c417dd143 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-link.md +++ b/deps/npm/docs/content/cli-commands/npm-link.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-link description: Symlink a package folder --- -# npm-link +# npm-link(1) ## Symlink a package folder @@ -33,7 +33,7 @@ of the current folder. Note that `package-name` is taken from `package.json`, not from directory name. -The package name can be optionally prefixed with a scope. See [`npm-scope`](npm-scope). +The package name can be optionally prefixed with a scope. See [`scope`](/using-npm/npm-scope). The scope must be preceded by an @-symbol and followed by a slash. When creating tarballs for `npm publish`, the linked packages are @@ -76,8 +76,7 @@ installation target into your project's `node_modules` folder. Note that in this case, you are referring to the directory name, `node-redis`, rather than the package name `redis`. -If your linked package is scoped (see [`npm-scope`](npm-scope)) your link command must -include that scope, e.g. +If your linked package is scoped (see [`scope`](/using-npm/npm-scope)) your link command must include that scope, e.g. ```bash npm link @myorg/privatepackage diff --git a/deps/npm/docs/content/cli-commands/npm-logout.md b/deps/npm/docs/content/cli-commands/npm-logout.md index 41858ead96..ca7d86f2d1 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-logout.md +++ b/deps/npm/docs/content/cli-commands/npm-logout.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-logout description: Log out of the registry --- -# npm-logout +# npm-logout(1) ## Log out of the registry @@ -40,7 +40,7 @@ it takes precedence. Default: The scope of your current project, if any, otherwise none. -If specified, you will be logged out of the specified scope. See [`npm-scope`](npm-scope). +If specified, you will be logged out of the specified scope. See [`scope`](/using-npm/npm-scope). ```bash npm logout --scope=@myco diff --git a/deps/npm/docs/content/cli-commands/npm-ls.md b/deps/npm/docs/content/cli-commands/npm-ls.md index fd3439abff..64a399155f 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-ls.md +++ b/deps/npm/docs/content/cli-commands/npm-ls.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-ls description: List installed packages --- -# npm-ls +# npm-ls(1) ## List installed packages diff --git a/deps/npm/docs/content/cli-commands/npm-org.md b/deps/npm/docs/content/cli-commands/npm-org.md index 30c5832b79..33db38d0f8 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-org.md +++ b/deps/npm/docs/content/cli-commands/npm-org.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-org description: Manage orgs --- -# npm-org +# npm-org(1) ## Manage orgs diff --git a/deps/npm/docs/content/cli-commands/npm-outdated.md b/deps/npm/docs/content/cli-commands/npm-outdated.md index 351ccee82d..c7934109dc 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-outdated.md +++ b/deps/npm/docs/content/cli-commands/npm-outdated.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-outdated description: Check for outdated packages --- -# npm-outdated +# npm-outdated(1) ## Check for outdated packages diff --git a/deps/npm/docs/content/cli-commands/npm-owner.md b/deps/npm/docs/content/cli-commands/npm-owner.md index 28660e8926..bc2fbc82fb 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-owner.md +++ b/deps/npm/docs/content/cli-commands/npm-owner.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-owner description: Manage package owners --- -# npm-owner +# npm-owner(1) ## Manage package owners ### Synopsis diff --git a/deps/npm/docs/content/cli-commands/npm-pack.md b/deps/npm/docs/content/cli-commands/npm-pack.md index 462191d736..acf18559c1 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-pack.md +++ b/deps/npm/docs/content/cli-commands/npm-pack.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-pack description: Create a tarball from a package --- -# npm-pack +# npm-pack(1) ## Create a tarball from a package diff --git a/deps/npm/docs/content/cli-commands/npm-ping.md b/deps/npm/docs/content/cli-commands/npm-ping.md index 203f1dbd78..93d18b57f8 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-ping.md +++ b/deps/npm/docs/content/cli-commands/npm-ping.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-ping description: Ping npm registry --- -# npm-ping +# npm-ping(1) ## Ping npm registry diff --git a/deps/npm/docs/content/cli-commands/npm-prefix.md b/deps/npm/docs/content/cli-commands/npm-prefix.md index 8a312beb18..b82fec663a 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-prefix.md +++ b/deps/npm/docs/content/cli-commands/npm-prefix.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-prefix description: Display prefix --- -# npm-prefix +# npm-prefix(1) ## Display prefix @@ -21,7 +21,7 @@ to contain a `package.json` file or `node_modules` directory, unless `-g` is also specified. If `-g` is specified, this will be the value of the global prefix. See -[`npm-config`](npm-config) for more detail. +[`npm config`](/cli-commands/npm-config) for more detail. ### See Also diff --git a/deps/npm/docs/content/cli-commands/npm-profile.md b/deps/npm/docs/content/cli-commands/npm-profile.md index 366a824b7c..9fe82cd2d3 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-profile.md +++ b/deps/npm/docs/content/cli-commands/npm-profile.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-profile description: Change settings on your registry profile --- -# npm-profile +# npm-profile(1) ## Change settings on your registry profile ### Synopsis @@ -49,7 +49,7 @@ you're using a non-npmjs registry. | updated | 2017-10-02T21:29:45.922Z | +-----------------+---------------------------+ ``` - + * `npm profile set <property> <value>`: Set the value of a profile property. You can set the following properties this way: email, fullname, homepage, freenode, twitter, github diff --git a/deps/npm/docs/content/cli-commands/npm-prune.md b/deps/npm/docs/content/cli-commands/npm-prune.md index 40619e650a..c6b61e62f8 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-prune.md +++ b/deps/npm/docs/content/cli-commands/npm-prune.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-prune description: Remove extraneous packages --- -# npm-prune +# npm-prune(1) ## Remove extraneous packages ### Synopsis diff --git a/deps/npm/docs/content/cli-commands/npm-publish.md b/deps/npm/docs/content/cli-commands/npm-publish.md index 35a28fb085..b9d0cf1449 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-publish.md +++ b/deps/npm/docs/content/cli-commands/npm-publish.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-publish description: Publish a package --- -# npm-publish +# npm-publish(1) ## Publish a package @@ -22,12 +22,10 @@ Publishes a package to the registry so that it can be installed by name. All files in the package directory are included if no local `.gitignore` or `.npmignore` file exists. If both files exist and a file is ignored by `.gitignore` but not by `.npmignore` then it will be included. See -[`npm-developers`](/docs/using-npm/developers) for full details on what's included in the published -package, as well as details on how the package is built. +[`developers`](/using-npm/developers) for full details on what's included in the published package, as well as details on how the package is built. By default npm will publish to the public registry. This can be overridden by -specifying a different default registry or using a [`npm-scope`](npm-scope) in the name -(see [`package.json`](/docs/configuring-npm/package-json)). +specifying a different default registry or using a [`scope`](/using-npm/npm-scope) in the name (see [`package.json`](/configuring-npm/package-json)). * `<folder>`: A folder containing a package.json file @@ -62,13 +60,13 @@ the specified registry. Once a package is published with a given name and version, that specific name and version combination can never be used again, even if -it is removed with [`npm-unpublish`](npm-unpublish). +it is removed with [`npm unpublish`](/cli-commands/npm-unpublish). As of `npm@5`, both a sha1sum and an integrity field with a sha512sum of the tarball will be submitted to the registry during publication. Subsequent installs will use the strongest supported algorithm to verify downloads. -Similar to `--dry-run` see [`npm-pack`](npm-pack), which figures out the files to be +Similar to `--dry-run` see [`npm pack`](/cli-commands/npm-pack), which figures out the files to be included and packs them into a tarball to be uploaded to the registry. ### See Also diff --git a/deps/npm/docs/content/cli-commands/npm-rebuild.md b/deps/npm/docs/content/cli-commands/npm-rebuild.md index aed9d4e897..414b9ca55a 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-rebuild.md +++ b/deps/npm/docs/content/cli-commands/npm-rebuild.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-rebuild description: Rebuild a package --- -# npm-rebuildd +# npm-rebuild(1) ## Rebuild a package @@ -18,9 +18,7 @@ alias: npm rb ### Description -This command runs the `npm build` command on the matched folders. This is useful -when you install a new version of node, and must recompile all your C++ addons with -the new binary. +This command runs the `npm build` command on the matched folders. This is useful when you install a new version of node, and must recompile all your C++ addons with the new binary. ### See Also diff --git a/deps/npm/docs/content/cli-commands/npm-repo.md b/deps/npm/docs/content/cli-commands/npm-repo.md index e0f65ce8ad..ad41ea5712 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-repo.md +++ b/deps/npm/docs/content/cli-commands/npm-repo.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-repo description: Open package repository page in the browser --- -# npm-repo +# npm-repo(1) ## Open package repository page in the browser diff --git a/deps/npm/docs/content/cli-commands/npm-restart.md b/deps/npm/docs/content/cli-commands/npm-restart.md index cfdede6471..d6d388b224 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-restart.md +++ b/deps/npm/docs/content/cli-commands/npm-restart.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-restart description: Restart a package --- -# npm-restart +# npm-restart(1) ## Restart a package @@ -42,7 +42,7 @@ behavior will be accompanied by an increase in major version number ### See Also * [npm run-script](/cli-commands/npm-run-script) -* [npm scripts](/cli-commands//docs/using-npm/scripts) +* [npm scripts](/using-npm/scripts) * [npm test](/cli-commands/npm-test) * [npm start](/cli-commands/npm-start) * [npm stop](/cli-commands/npm-stop) diff --git a/deps/npm/docs/content/cli-commands/npm-root.md b/deps/npm/docs/content/cli-commands/npm-root.md index dc766a7b09..2b27878af4 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-root.md +++ b/deps/npm/docs/content/cli-commands/npm-root.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-root description: Display npm root --- -# npm-root +# npm-root(1) ## Display npm root diff --git a/deps/npm/docs/content/cli-commands/npm-run-script.md b/deps/npm/docs/content/cli-commands/npm-run-script.md index a6df4befac..51def74c3c 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-run-script.md +++ b/deps/npm/docs/content/cli-commands/npm-run-script.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-run-script description: Run arbitrary package scripts --- -# npm-run-script +# npm-run-script(1) ## Run arbitrary package scripts diff --git a/deps/npm/docs/content/cli-commands/npm-search.md b/deps/npm/docs/content/cli-commands/npm-search.md index 6182660e3c..e066106faf 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-search.md +++ b/deps/npm/docs/content/cli-commands/npm-search.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-search description: Search for packages --- -# npm-search +# npm-search(1) ## Search for packages diff --git a/deps/npm/docs/content/cli-commands/npm-shrinkwrap.md b/deps/npm/docs/content/cli-commands/npm-shrinkwrap.md index f8ae984e42..342fb00167 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-shrinkwrap.md +++ b/deps/npm/docs/content/cli-commands/npm-shrinkwrap.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-shrinkwrap description: Lock down dependency versions for publication --- -# npm-shrinkwrap +# npm-shrinkwrap(1) ## Lock down dependency versions for publication @@ -20,7 +20,7 @@ This command repurposes `package-lock.json` into a publishable `npm-shrinkwrap.json` or simply creates a new one. The file created and updated by this command will then take precedence over any other existing or future `package-lock.json` files. For a detailed explanation of the design and purpose -of package locks in npm, see [npm-package-locks](npm-package-locks). +of package locks in npm, see [package-locks](/configuring-npm/package-locks). ### See Also diff --git a/deps/npm/docs/content/cli-commands/npm-star.md b/deps/npm/docs/content/cli-commands/npm-star.md index c50c7ca17a..1912e9c654 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-star.md +++ b/deps/npm/docs/content/cli-commands/npm-star.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-star description: Mark your favorite packages --- -# npm-star +# npm-star(1) ## Mark your favorite packages diff --git a/deps/npm/docs/content/cli-commands/npm-stars.md b/deps/npm/docs/content/cli-commands/npm-stars.md index 9e1c7e1edd..475547bb4b 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-stars.md +++ b/deps/npm/docs/content/cli-commands/npm-stars.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-stars description: View packages marked as favorites --- -# npm-stars +# npm-stars(1) ## View packages marked as favorites diff --git a/deps/npm/docs/content/cli-commands/npm-start.md b/deps/npm/docs/content/cli-commands/npm-start.md index 23cf3d9017..839528257b 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-start.md +++ b/deps/npm/docs/content/cli-commands/npm-start.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-start description: Start a package --- -# npm-start +# npm-start(1) ## Start a package @@ -21,8 +21,7 @@ its `"scripts"` object. If no `"start"` property is specified on the `"scripts"` object, it will run `node server.js`. As of [`npm@2.0.0`](https://blog.npmjs.org/post/98131109725/npm-2-0-0), you can -use custom arguments when executing scripts. Refer to [`npm-run-script`](npm-run-script) for -more details. +use custom arguments when executing scripts. Refer to [`npm run-script`](/cli-commands/npm-run-script) for more details. ### See Also diff --git a/deps/npm/docs/content/cli-commands/npm-stop.md b/deps/npm/docs/content/cli-commands/npm-stop.md index 49a7416464..da759047cb 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-stop.md +++ b/deps/npm/docs/content/cli-commands/npm-stop.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-stop description: Stop a package --- -# npm-stop +# npm-stop(1) ## Stop a package diff --git a/deps/npm/docs/content/cli-commands/npm-team.md b/deps/npm/docs/content/cli-commands/npm-team.md index dda840d1df..9a63b10c26 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-team.md +++ b/deps/npm/docs/content/cli-commands/npm-team.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-team description: Manage organization teams and team memberships --- -# npm-team +# npm-team(1) ## Manage organization teams and team memberships @@ -28,13 +28,10 @@ Used to manage teams in organizations, and change team memberships. Does not handle permissions for packages. Teams must always be fully qualified with the organization/scope they belong to -when operating on them, separated by a colon (`:`). That is, if you have a -`developers` team on a `foo` organization, you must always refer to that team as -`foo:developers` in these commands. +when operating on them, separated by a colon (`:`). That is, if you have a `wombats` team in a `wisdom` organization, you must always refer to that team as `wisdom:wombats` in these commands. * create / destroy: - Create a new team, or destroy an existing one. - + Create a new team, or destroy an existing one. Note: You cannot remove the `developers` team, <a href="https://docs.npmjs.com/about-developers-team" target="_blank">learn more.</a> * add / rm: Add a user to an existing team, or remove a user from a team they belong to. diff --git a/deps/npm/docs/content/cli-commands/npm-test.md b/deps/npm/docs/content/cli-commands/npm-test.md index a34c2f88de..99c027e3e0 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-test.md +++ b/deps/npm/docs/content/cli-commands/npm-test.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-test description: Test a package --- -# npm-test +# npm-test(1) ## Test a package diff --git a/deps/npm/docs/content/cli-commands/npm-token.md b/deps/npm/docs/content/cli-commands/npm-token.md index 4e3819f155..37a74083d2 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-token.md +++ b/deps/npm/docs/content/cli-commands/npm-token.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-token description: Manage your authentication tokens --- -# npm-token +# npm-token(1) ## Manage your authentication tokens @@ -64,5 +64,5 @@ This lets you list, create and revoke authentication tokens. * `npm token revoke <token|id>`: This removes an authentication token, making it immediately unusable. This can accept both complete tokens (as you get back from `npm token create` and will - find in your `.npmrc`) and ids as seen in the `npm token list` output. + find in your `.npmrc`) and ids as seen in the `npm token list` output. This will NOT accept the truncated token found in `npm token list` output. diff --git a/deps/npm/docs/content/cli-commands/npm-uninstall.md b/deps/npm/docs/content/cli-commands/npm-uninstall.md index f18239e88b..96fdc4ebe0 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-uninstall.md +++ b/deps/npm/docs/content/cli-commands/npm-uninstall.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-uninstall description: Remove a package --- -# npm-uninstall +# npm-uninstall(1) ## Remove a package @@ -44,7 +44,7 @@ the package version in your main package.json: Further, if you have an `npm-shrinkwrap.json` then it will be updated as well. -Scope is optional and follows the usual rules for [`npm-scope`](snpm-scope). +Scope is optional and follows the usual rules for [`scope`](/using-npm/scope). Examples: ```bash diff --git a/deps/npm/docs/content/cli-commands/npm-unpublish.md b/deps/npm/docs/content/cli-commands/npm-unpublish.md index 0ad7e687cf..5348023d9a 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-unpublish.md +++ b/deps/npm/docs/content/cli-commands/npm-unpublish.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-unpublish description: Remove a package from the registry --- -# npm-unpublish +# npm-unpublish(1) ## Remove a package from the registry @@ -43,7 +43,7 @@ only allowed with versions published in the last 72 hours. If you are trying to unpublish a version published longer ago than that, contact support@npmjs.com. -The scope is optional and follows the usual rules for [`npm-scope`](/docs/using-npm/scope). +The scope is optional and follows the usual rules for [`scope`](/using-npm/scope). ### See Also diff --git a/deps/npm/docs/content/cli-commands/npm-update.md b/deps/npm/docs/content/cli-commands/npm-update.md index 8203f98f65..f2e93b6dc3 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-update.md +++ b/deps/npm/docs/content/cli-commands/npm-update.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-update description: Update a package --- -# npm-update +# npm-update(1) ## Update a package @@ -35,8 +35,8 @@ As of `npm@2.6.1`, the `npm update` will only inspect top-level packages. Prior versions of `npm` would also recursively inspect all dependencies. To get the old behavior, use `npm --depth 9999 update`. -As of `npm@5.0.0`, the `npm update` will change `package.json` to save the -new version as the minimum required dependency. To get the old behavior, +As of `npm@5.0.0`, the `npm update` will change `package.json` to save the +new version as the minimum required dependency. To get the old behavior, use `npm update --no-save`. ### Example diff --git a/deps/npm/docs/content/cli-commands/npm-version.md b/deps/npm/docs/content/cli-commands/npm-version.md index 9b7b788100..a47e9e3332 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-version.md +++ b/deps/npm/docs/content/cli-commands/npm-version.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-version description: Bump a package version --- -# npm-version +# npm-version(1) ## Bump a package version @@ -98,7 +98,7 @@ and tag up to the server, and deletes the `build/temp` directory. * Default: false * Type: Boolean -Prevents throwing an error when `npm version` is used to set the new version +Prevents throwing an error when `npm version` is used to set the new version to the same value as the current version. #### git-tag-version @@ -129,6 +129,6 @@ Note that you must have a default GPG key set up in your git config for this to * [npm init](/cli-commands/npm-init) * [npm run-script](/cli-commands/npm-run-script) * [npm scripts](/using-npm/scripts) -* [package.json](/docs/configuring-npm/package-json) +* [package.json](/configuring-npm/package-json) * [semver](/using-npm/semver) * [config](/using-npm/config) diff --git a/deps/npm/docs/content/cli-commands/npm-view.md b/deps/npm/docs/content/cli-commands/npm-view.md index 97cf28ecfe..0c108e6f56 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-view.md +++ b/deps/npm/docs/content/cli-commands/npm-view.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-view description: View registry info --- -# npm-view +# npm-view(1) ## View registry info @@ -80,7 +80,7 @@ npm view express contributors.name contributors.email "Person" fields are shown as a string if they would be shown as an object. So, for example, this will show the list of npm contributors in -the shortened string format. (See [`package.json`](/docs/configuring-npm/package.json) for more on this.) +the shortened string format. (See [`package.json`](/configuring-npm/package.json) for more on this.) ```bash npm view npm contributors @@ -92,7 +92,7 @@ was required by each matching version of yui3: ```bash npm view yui3@'>0.5.4' dependencies.jsdom -``` +``` To show the `connect` package version history, you can do this: diff --git a/deps/npm/docs/content/cli-commands/npm-whoami.md b/deps/npm/docs/content/cli-commands/npm-whoami.md index 2ef2ff0ee6..b0eda4e46a 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm-whoami.md +++ b/deps/npm/docs/content/cli-commands/npm-whoami.md @@ -1,10 +1,10 @@ --- -section: cli-commands +section: cli-commands title: npm-whoami description: Display npm username --- -# npm-whoami +# npm-whoami(1) ## Display npm username ### Synopsis diff --git a/deps/npm/docs/content/cli-commands/npm.md b/deps/npm/docs/content/cli-commands/npm.md index 2b18c971ae..01a9308204 100755..100644 --- a/deps/npm/docs/content/cli-commands/npm.md +++ b/deps/npm/docs/content/cli-commands/npm.md @@ -1,10 +1,11 @@ --- -section: cli-commands +section: cli-commands title: npm description: javascript package manager --- -# npm +# npm(1) + ## javascript package manager ### Synopsis @@ -44,7 +45,7 @@ terms of use. You probably got npm because you want to install stuff. Use `npm install blerg` to install the latest version of "blerg". Check out -[`npm-install`](npm-install) for more info. It can do a lot of stuff. +[`npm install`](/cli-commands/npm-install) for more info. It can do a lot of stuff. Use the `npm search` command to show everything that's available. Use `npm ls` to show everything you've installed. @@ -67,7 +68,7 @@ the [node-gyp Wiki](https://github.com/TooTallNate/node-gyp/wiki). ### Directories -See [`npm-folders`](/docs/configuring-npm/folders) to learn about where npm puts stuff. +See [`folders`](/configuring-npm/folders) to learn about where npm puts stuff. In particular, npm has two modes of operation: @@ -88,7 +89,7 @@ If you're using npm to develop and publish your code, check out the following help topics: * json: - Make a package.json file. See [`package.json`](/docs/configuring-npm/package.json). + Make a package.json file. See [`package.json`](/configuring-npm/package.json). * link: For linking your current working code into Node's path, so that you don't have to reinstall every time you make a change. Use @@ -129,7 +130,7 @@ npm is extremely configurable. It reads its configuration options from npm's default configuration options are defined in lib/utils/config-defs.js. These must not be changed. -See [`npm-config`](/docs/using-npm/config) for much much more information. +See [`config`](/using-npm/config) for much much more information. ### Contributions @@ -139,8 +140,7 @@ If you would like to contribute, but don't know what to work on, read the contributing guidelines and check the issues list. * [CONTRIBUTING.md](https://github.com/npm/cli/blob/latest/CONTRIBUTING.md) -* [Bug tracker](https://npm.community/c/bugs) -* [Support tracker](https://npm.community/c/support) +* [Bug tracker](https://github.com/npm/cli/issues) ### Bugs |