chore: add fetch package support metadata - #113
Open
sh962214-hub wants to merge 1 commit into
Open
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
1 participant
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.
Summary
homepagemetadata for@better-fetch/fetchbugs.urlmetadata pointing to the repository issue trackerWhy
The package already declares its repository and package directory, but the published npm metadata does not expose direct README/support links. These fields help npm users find the package docs and report issues from package manager metadata.
Validation
packages/better-fetch/package.jsonwith Nodehomepageandbugs.urlvaluesgit diff --checkNo runtime code, dependencies, exports, or build outputs were changed.