Strategy for original `rustfmt` crate on crates.io
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 24
Description
There's an ancient rustfmt crate on crates.io in addition to the current/maintained rustfmt-nightly crate, and the former's latest version is v0.10.0 which was published over 2.5 years ago.
This has been a source of confusion for users, particularly those new to the Rust ecosystem who go to crates.io looking for rustfmt, so I'm wondering if we should try to deprecate it/yank versions or if there's some valid usage patterns for that crate I'm just not aware of.
Thoughts?
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 by reviewing the original rustfmt crate and rustfmt-nightly crate pages on crates.io, then read the issue discussion about valid usage patterns. The work is done when maintainers decide and document a clear strategy for the old crate, such as deprecation, yanking versions, or retaining it for a stated reason.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100