docs(package-json): clarify repository field normalization #8799
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.
Description
This PR documents npm's normalization behavior for the
repositoryfield inpackage.jsonduring publishing.Changes
npm publishnpm pkg fixas a tool to automatically convert to normalized formatContext
Users were confused when
npm publishshowed warnings about auto-correcting therepositoryfield, even though the documentation stated shorthand formats were allowed. The maintainer (@wraithgar) explained that npm has historically normalized this field during publishing, creating a discrepancy between localpackage.jsonand the published manifest. The warning is preparing users for future changes where this discrepancy may no longer be allowed.Closes #7299