Lorenzo (Feb 04 2025 at 13:44): Lorenzo (Feb 04 2025 at 13:44):I have two questions regarding packages with wasm components:
Is there a public warg/wasm-component registry, e.g. equivalent of crates.io or NPM, where anyone can register & publish packages to? Is this wasi.dev? -- if so, it doesn't look like a registry, but rather a docs page?
If there's no central public registry, then the applications would have to manage auth and publishing rights. In this case, I'm curious if someone has opinions or thoughts on this: if you were creating an application where users can publish packages to a warg registry, how would you structure package names & namespaces?
For example it could be in the format {username}:{package-name} so that users have full control over both the namespace (as it is their username that they pick when signing up to the app) and the package name. The problem with this is that if someone has the username that already is used from a 'default' registry then it can cause conflicts, for example if someone registers the username of 'wasi' or 'wasm'.
It could also be formatted as app-name-{username}:{package-name} to workaround that previous issue.
It alternatively be formatted as app-name:user-name-{package-name}. Or also just app-name:{package-name} but then there's no namespacing between users.
Just wondering if there are any suggestions or best practices with this.
Calvin Prewitt (Feb 04 2025 at 14:36):No official, central registry. The tooling today largely supports any OCI registries and Warg registries.
The closest thing you may find useful is https://wa.dev/
You can create namespaces and packages and manage user access. Feel free to DM me if you have questions about that service.
Last updated: Feb 27 2025 at 23:03 UTC