chore(package): fix repository url; add homepage and bugs urls #1673
Conversation
This file contains 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
Fdawgs
changed the title
|
hey sorry I was out sick and this completely missed this - if you wouldn't mind re-opening and running |
|
No worries @G-Rath, I was just doing a pre-Christmas/New Year clean of my forks. I'll open a new PR! |
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.
The repository URL was fixed by simply running
npm pkg fix, which is whatnpm publishdoes prior to publishing.The addition of the
homepageproperty allows for the URL to the repo to be correctly displayed when hovered over in VS Code when using a proxy registry like in Azure DevOps:Compared to eslint-plugin-regexp, which does have the homepage set:
The
bugsproperty was also added to allow fornpm bugsto work.