docs: add hash to "tag" config link#5519
Merged
lukekarrys merged 4 commits intonpm:latestfrom Sep 21, 2022
Merged
Conversation
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)
wraithgar
approved these changes
Sep 15, 2022
Member
wraithgar
left a comment
wraithgar
left a comment
There was a problem hiding this comment.
Really helpful change.
We do this in other places such as on package-spec when we link into the registry config specifically. Probably lots more places we could do this too.
Contributor
Author
|
@wraithgar, your "lots more places we could do this too" comment inspired me to dig around a little, I added a few more changes to this PR -- almost added a bunch more, but I'll open another PR for the rest so this one doesn't get out of hand. I used this search: I ran across a non-standard "See also" footer, I used this search to make sure there weren't any others (nope): |
mrienstra
changed the title
wraithgar
approved these changes
Sep 19, 2022
lukekarrys
changed the title
This was referenced Nov 5, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Minor change.
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)
References