Publish to deno.land/x

[yuhr]

runtypes is now migrating to Deno-first project. The substantial work to the codebase is already done by #339, so actually this project is already Deno-first, but it's yet to publish to deno.land/x due to inactivity of @pelotom on GitHub. I'm now trying to contact with him by email, sending following message:

The important thing is, runtypes is now going to be a Deno-first project. Being Deno-first doesn't actually necessitates publishing to deno.land/x, but it's highly favored. This needs changes to owner-level settings and collaboration with @sant123 who has already been using runtypes name in deno.land/x. Could you take some time to do this yourself, or leave this to me by transferring ownership of pelotom/runtypes to me (yuhr/runtypes) or an organization (runtypes/runtypes) with me being a co-owner?

To be clear, migrating to a Deno-first project doesn't imply stopping publishing the library to www.npmjs.com. There's a build tool to easily generate npm packages from Deno-first projects, namely dnt, thus it'll still be available to Node.js.

As mentioned in the quote, previously there's unofficial releases of this library in deno.land/x managed by @sant123. Hopefully this will be replaced by our releases.

[sant123]

Now that JSR is out. It would be worth to publish runtypes on the new registry too.

[yuhr]

The repository has been successfully moved to a new organization, and I'm now co-owner of this repository. I’d like to use this place to thank pelotom for the quick reply! I'm going to take a look at settings in this weekend.

[yuhr]

As expected, setting up the webhook without contacting support results in an error:

{"success":false,"error":"module name is registered to a different repository"}

So I've sent an email to modules@deno.com. Q&A says “please contact support” but I couldn't find where to do so; instead I found the address in SO, so I'm unsure if this is the correct way to make such a request, but I see no other promising way out there.

The message I wrote is:

My case is that I've got a co-ownership of an OSS called runtypes (whose original owner has been inactive for years), and I'm now going to publish the library to deno.land/x, but there's unofficial releases tied to sant123/runtypes (whose owner is another from the original owner). I already got the agreement on this with sant123, so could you change the associated repository to the official one? The webhook is set up, thus now I think all we need is your manual support to change that.

[sant123]

I think the easiest solution for this is to create a scope and package on jsr.io. Since deno.land/x in some moment will stop being the preferred way to publish third party modules, you can start supporting the package in there. Also jsr supports members for publishing so this type of issue won’t be a problem anymore.