Skip to content

Commit

Permalink
docs: add hash to "tag" config link (#5519)
Browse files Browse the repository at this point in the history
* docs: add hash to "tag" config link

Minor change.

[using-npm/config](https://docs.npmjs.com/cli/v8/using-npm/config) is a long page -- heck, the subtitle is "More than you probably want to know about npm configuration" -- so instead of dumping people at the top of it when they follow the link to learn about the "tag" config, let's send 'em right to the relevant bit.

Aside from it being a long page, one more motivation: trying to get to the section by searching is also slow, it's the 16th (of 24) occurrence of "tag" on the page. (though to be fair, only the 4th if they catch it in the table of contents)

* docs: fix some nonstandard formatting

* docs: more useful link

Co-authored-by: Luke Karrys <[email protected]>
  • Loading branch information
mrienstra and lukekarrys authored Sep 21, 2022
1 parent 5645c51 commit 8743366
Show file tree
Hide file tree
Showing 4 changed files with 6 additions and 6 deletions.
2 changes: 1 addition & 1 deletion docs/content/commands/npm-adduser.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ Note: This command is unaware of workspaces.

Create a new user in the specified registry, and save the credentials to
the `.npmrc` file. If no registry is specified, the default registry
will be used (see [`config`](/using-npm/config)).
will be used (see [`registry`](/using-npm/registry)).

When using `legacy` for your `auth-type`, the username, password, and
email are read in from prompts.
Expand Down
2 changes: 1 addition & 1 deletion docs/content/commands/npm-config.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ variables, `npmrc` files, and in some cases, the `package.json` file.
See [npmrc](/configuring-npm/npmrc) for more information about the npmrc
files.
See [config(7)](/using-npm/config) for a more thorough explanation of the
See [config](/using-npm/config) for a more thorough explanation of the
mechanisms involved, and a full list of config options available.
The `npm config` command can be used to update and edit the contents
Expand Down
2 changes: 1 addition & 1 deletion docs/content/commands/npm-install.md
Original file line number Diff line number Diff line change
Expand Up @@ -127,7 +127,7 @@ into a tarball (b).
* `npm install [<@scope>/]<name>`:

Do a `<name>@<tag>` install, where `<tag>` is the "tag" config. (See
[`config`](/using-npm/config). The config's default value is `latest`.)
[`config`](/using-npm/config#tag). 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.
Expand Down
6 changes: 3 additions & 3 deletions docs/content/using-npm/package-spec.md
Original file line number Diff line number Diff line change
Expand Up @@ -101,6 +101,6 @@ Examples:

### See also

[npm-package-arg](https://npm.im/npm-package-arg)
[scope](/using-npm/scope)
[config](/using-npm/config)
* [npm-package-arg](https://npm.im/npm-package-arg)
* [scope](/using-npm/scope)
* [config](/using-npm/config)

0 comments on commit 8743366

Please sign in to comment.