Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

New service: JSR #10007

Open
chris48s opened this issue Mar 2, 2024 · 1 comment
Open

New service: JSR #10007

chris48s opened this issue Mar 2, 2024 · 1 comment
Labels
service-badge Accepted and actionable changes, features, and bugs

Comments

@chris48s
Copy link
Member

chris48s commented Mar 2, 2024

馃搵 Description

https://jsr.io/ is a JS/TS registry from the creators of deno
Announcement: https://deno.com/blog/jsr_open_beta

馃敆 Data

https://jsr.io/docs/api

Interestingly, JSR has two APIs we could use

There's what I'm going to call a "native" API
https://jsr.io/docs/api#jsr-registry-api

but then there is the "npm compatibility registry API"
https://jsr.io/docs/api#npm-compatibility-registry-api

The interesting thing about this is it serves up JSR data in the same response format as NPM's API so in theory we should be able to re-use the code for our suite of NPM badges to also cover JSR quite easily.

Unfortunately, although the response format is supposed to be the same, the URL schema isn't so you can't just plug in ?registry_uri=https%3A%2F%2Fnpm.jsr.io to our existing NPM badges and have them work out of the box.

馃帳 Motivation

I don't especially want to use this myself but I figure its useful to have a tracking issue for it.

@chris48s chris48s added the service-badge Accepted and actionable changes, features, and bugs label Mar 2, 2024
@LitoMore
Copy link
Contributor

LitoMore commented May 4, 2024

JSR has already implemented shields.io. See here: https://jsr.io/docs/badges

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
service-badge Accepted and actionable changes, features, and bugs
Projects
None yet
Development

No branches or pull requests

2 participants