Shall `wasm32-wasi`-related messages be improved?
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
Problem you are trying to solve
$ rustup update nightly
info: syncing channel updates for 'nightly-x86_64-unknown-linux-gnu'
info: latest update on 2024-11-25, rust version 1.85.0-nightly (28fc2ba71 2024-11-24)
info: skipping nightly which is missing installed component 'rust-std-wasm32-wasi'
info: syncing channel updates for 'nightly-2024-11-24-x86_64-unknown-linux-gnu'
info: syncing channel updates for 'nightly-2024-11-23-x86_64-unknown-linux-gnu'
info: latest update on 2024-11-23, rust version 1.85.0-nightly (a47555110 2024-11-22)
info: skipping nightly which is missing installed component 'rust-std-wasm32-wasi'
...
Nightly update falls back (probably because of WASI target changes).
Solution you'd like
Shall rustup include a helpful message for wasm32-wasi specifically, mentioning that now one should write wasm32-wasip1?
Or maybe even automatically migrate to it.
Notes
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the rustup update nightly path that reports a missing rust-std-wasm32-wasi component, then review how target names are presented during fallback. Done means the wasm32-wasi case gives clear guidance toward wasm32-wasip1, with the intended behavior for automatic migration explicitly resolved and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100