Support JSR

[hckhanh]

You can take a look at: https://jsr.io/

[halfbyte]

@hckhanh Thanks for the feedback. We've been asked about that by another client as well. This will take a while for us to implement, because jsr heavily relies on using the npm: scoping and we don't fully support that yet.

I've started to look at it today but this is a bit complex, because we'll probably need to introduce the concept of a package alias or "real name" in quite a few places in the Depfu machinery.

I'll report my progress here.

[halfbyte]

Quick update on this: I think we're finally at a stage where I'll be testing this with actual repos and see if there are any remaining issues.

So far this seems to work for all three JS package managers we support: npm, yarn (also with yarn berry), and pnpm. We're going to deploy this hopefully by the end of the week unless I issues. There may be issues with the way we display these updates on the dashboard and in pull requests for a while, feel free to report them here.

(I'll update this issue as soon as we deploy this to production)

[halfbyte]

Just a quick heads up: Unfortunately, the jsr.io APIs are somewhat limited in the information they share. For example, even though the registry clearly has information about github URLs for packages (As can be seen here for example), it is not returned in the API, neither for the native JSR API nor for the npm compatibility API which we are using.

This means that, unfortunately, we won't be able to retrieve change information for JSR packages until JSR includes this data in their API. I am not willing to start scraping their web interface for these informations.

I've opened up an issue with jsr so let's see how that goes.

[halfbyte]

If you want to try it out even without changelog info, aliased packages should now work and thus jsr.io should work. Please note that you will have to have an .npmrc or the yarn berry equivalent in your repository that maps the @jsr scope to the jsr registry.

[halfbyte]

(I'm keeping this open for now to see if JSR is willing to address my issue)

[hckhanh]

Thank you @halfbyte

[hckhanh]

Ah you should report directly to them by email. It can be faster.
Last year I reported a bug to them by email: help@jsr.io
@halfbyte