Repository navigation
chore(repo): link npm pages to the docs and add search keywords - #12
Merged
Merged
Conversation
Signed-off-by: MobileMage <aidelojejoshua@gmail.com>
MobileMage
changed the title
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.
Before the first npm release, each package gets a
homepagethat points to itsguide on the docs site, and keywords that match what people search for, such as
nigeria-postcodeandpostcode-validation. npm shows both on the package pageand uses the keywords in its search. A change file marks a patch for each package.
No code changes.
Signed-off-by: MobileMage aidelojejoshua@gmail.com