Repository navigation
Add license, language and npm download badges to package READMEs - #59
Merged
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.
Both package READMEs now place a centered badge row immediately below the title, matching the style used by other oe repositories. Each row shows main-branch CI, TypeScript, the MIT license, the package's current npm version and monthly npm downloads, with package-specific links and accessible labels.
Validation: checked the two five-badge blocks, package/source/license links and whitespace. All eight distinct badge URLs returned valid SVGs with the expected labels; both version badges show v3.0.0 and both license badges show MIT. Documentation only; no runtime or package-version changes. npm README pages receive the new markup on the next package publication.