-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DOCS] package.json#repository should clarify normalization steps and future plans. #7299
Comments
Historically npm has normalized that entry when publishing a package, which lead to a discrepancy between what was in the package.json and what was in the manifest on the registry. This warning is showing that change happening. At some point in the future we are hoping to stop allowing those fields to differ, so the warning is letting folks clean things up now. The docs will likely need to be updated on this to reflect the new reality. |
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
My repo's
package.json
file has a"repository"
field set to"JoshuaKGoldberg/emojipedia"
as a shorthand.npm publish
still works, but gives this complaint:https://github.com/JoshuaKGoldberg/emojipedia/blob/7b67fe1986852fb271c2eab59fe536ee3476322f/package.json#L5
Expected Behavior
Per npm/npm#3783 -> https://docs.npmjs.com/cli/v10/configuring-npm/package-json#repository, using a repository shorthand like
"JoshuaKGoldberg/emojipedia"
should be allowed.Steps To Reproduce
package.json
's"repository"
value is a GitHub string shorthandnpm publish
Environment
The text was updated successfully, but these errors were encountered: