fix: correct repository, homepage, and bugs URLs in package.json - #25
Merged
Conversation
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
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.
Why
package.json points repository, homepage, and bugs at github.com/briansparker/You, which is not this repository. Once the package is published to npm, these fields drive the links shown on the npm package page, so they should be correct before the first publish.
What changed
Validation
Publish readiness notes
The rest of the manifest already looks publish-ready: files whitelist covers dist and bin, both bin entries exist, and prepublishOnly runs build plus tests. Two things to know before running npm publish: