docs(npmrc): add example of URI fragment limitations #8099
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.
Attempt to clarify limitations of how URI Fragments are not applied at the host level but at the path level and are not recursively applied to any sub-path.
When attempting to generate valid npmrc configuration files by using //host.name/:_auth=$token to cover any registry available at that host, I could not get npm to use those credentials.
I figured out the hard way that npm would only use the credentials if I specified the entire path up to the registry name i.e. //host.name/artifactory/api/npm/:auth=$token.
I felt the docs could be clarified to help other users realise the same.
Note: This PR replaces #8095 since I messed up the git commits and were unable to clean it up.