WebAssembly / WebAssembly/component-model
What is today's guidance for naming packages?
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 1.4k
- Forks
- 130
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 15
Description
If I'm creating a WIT package today, how should I go about choosing a name for it such that it won't conflict with somebody else's name in the future? Is there a warg instance running somewhere that has a namespace allocated to it and whose database won't be purged in the future?
Currently, I'm following the lead of the wasi crate and using a package name of rust:<pkg> where <pkg> is the name of a crate I control on crates.io.
Contributor guide
No contributing guide indexed for this repository
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 by reviewing the linked wasi/wit/wasi-crate.wit example and the current WIT package naming conventions. Investigate whether a persistent warg instance and allocated namespace exist, then document the current recommendation for choosing a package name and explain how the rust: convention relates to crates.io.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- developer-experience, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100