Repository navigation
docs: fix the install size badge and the coverage badge link - #2
Merged
Merged
Conversation
packagephobia.com now answers every request, badges included, with a 429 bot checkpoint page, so the badge never rendered. Shields reads the unpacked size from the npm registry; with no dependencies that is the install size. The coverage badge linked to the literal text npm-coverage-url.
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.
429Vercel bot-checkpoint page, so the badge never rendered on GitHub or npm. It now usesimg.shields.io/npm/unpacked-size, which reads the npm registry directly (currently 20.6 kB). abtestify has no dependencies, so that is its install size.npm-coverage-url, because it used()where it should have used[].I checked both badges through GitHub's image proxy.