You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
馃搵 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.
The text was updated successfully, but these errors were encountered: