Skip to content

Improve ergonomics of Rust examples, re-enable use of published packages #255

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
vados-cosmonic opened this issue May 7, 2025 · 0 comments

Comments

@vados-cosmonic
Copy link
Collaborator

This issue arguably shouldn't go here, but currently UX issues in upstream tooling is making the Rust

The goal is to revert this reverted functionality -- we want to be able to use published WIT packages but there are a few issues stopping us:

  • cargo-component does not configure/patch where wkg looks for deps (the target kind) when configured in Cargo.toml (i.e. we should be able to specify that docs is a known package w/ a known registry)
  • cargo-component currently does not properly resolve targets w/ multiple worlds even if wkg is configured (via it's global config file)
  • wkg should be able to use local fconfig

There are at least a few ways to solve this issue:

  1. Update cargo-component to perform the patching of registries for namespaces before using wasm-pkg-tools functionality
  2. Update wkg to prefer local config files and include one in the tutorial code
  3. Update the guide to get users to configure wkg global config before attempting usage.

A somewhat hidden requirement/sidequest to this issue is that we need more cargo-component/wasm-pkg-tools maintainers. The current functionality is fantastic for these tools, but the UX needs to be polished just a bit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant