Request for Mirror Synchronization Capability about jsr

[elrrrrrrr]

@lucacasonato

🤩

Here is the REPLICATE-API interface, which returns corresponding changes through a stream.

https://registry.npmmirror.com/_changes?since=1, we have also developed our own changesStream interface, which returns changes in JSON format, It also requires a since parameter for pagination.

Additionally, we noticed that the manifest does not contain data related to maintainers, which might introduce some differences. If there are already existing interfaces for updates, please inform us how to call them.

Lastly, we hope to find a way to return all npm tarball list for initialization purposes. such as ref .

[lucacasonato]

Hey @elrrrrrrr

Yes we'd love to support whatever is necessary to support mirroring. I am not sure if we can provide that exact replicate.npmjsr.com interface, just because I think it may be tied to NPM's usage of couchdb? Do you know if there are docs on this?

Would an alternative change stream also work? We could provide a way for you to query the registry API for new NPM tarballs + updates to NPM version manifests (in a change stream style format). Let me know what exact info you need in the change stream :)

[elrrrrrrr]

🎉 We've been attempting some synchronization and adaptation work locally and have successfully completed it for a single package, happ pass.

Here are some of the services or changes we urgently need:

1. Maintainers in manifests, (all packages in the npm registry have maintainers information even security holder). Are there any plans to add a default value for this field, maybe like [email protected]?
2. There is a need for a way to export the names of all existing packages for init the mirror.
3. We need a changesStream service. Currently, it seems PACKAGE_VERSION_ADD event is enough ?

🚀 we are eagerly anticipating the launch of the jsr mirror service as soon as possible.