Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
I think we can synchronize the functionality in the documentation. |
|
would you mind adding some links to show what they look like? I'm wondering whether it's worth adding so many different badges when there are already badge apis ... but that's only a slight niggle - would love to know what folk think |
|
Can we get a docs preview please? 🙏 Locally the |
|
I find it very useful to centralize every badges into one platform, specially if we are on our way to centralize all npm-related data. It's a bit annoying to search for a given badge, like downloads per week ; searching for a good one, having it down or unmaintained sometimes... Make sense to take care of it in npmx imo. Love the badges color btw, they look awesome ! I'm just not sure about contrast issues on the orange and green ones. Might be worth asking our a11y experts. |
# Conflicts: # server/api/registry/badge/[...pkg].get.ts
# Conflicts: # docs/content/2.guide/1.features.md
Co-authored-by: Daniel Roe <daniel@roe.dev>
Co-authored-by: Daniel Roe <daniel@roe.dev>

Description
Implement new API endpoint for badges with these different types:
Thoughts
versionwill be returned and if a specific version is specified without/version/, it tries to match the route to the[type]route, so it fails. IMO we should drop the old route entirely to keep it clean and maintainable.Examples
Here are some example badges: