You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 ifwkg 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:
Update cargo-component to perform the patching of registries for namespaces before using wasm-pkg-tools functionality
Update wkg to prefer local config files and include one in the tutorial code
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.
The text was updated successfully, but these errors were encountered:
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 wherewkg
looks for deps (the target kind) when configured inCargo.toml
(i.e. we should be able to specify thatdocs
is a known package w/ a known registry)cargo-component
currently does not properly resolve targets w/ multiple worlds even ifwkg
is configured (via it's global config file)wkg
should be able to use local fconfigThere are at least a few ways to solve this issue:
cargo-component
to perform the patching of registries for namespaces before usingwasm-pkg-tools
functionalitywkg
to prefer local config files and include one in the tutorial codewkg
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.The text was updated successfully, but these errors were encountered: