30 lines
1021 B
Markdown
30 lines
1021 B
Markdown
# 029 — Remove unused crates and dependencies
|
|
|
|
## Summary
|
|
|
|
Audit `Cargo.toml` and `webapp/package.json` for dependencies that are
|
|
declared but not actually used, and remove them.
|
|
|
|
## Scope
|
|
|
|
- Check each `[dependencies]`/`[dev-dependencies]` entry in `Cargo.toml`
|
|
against actual usage (e.g. `cargo +nightly udeps`, or grepping for each
|
|
crate's root module name), same for `webapp/package.json` (e.g. `npx
|
|
depcheck`).
|
|
- Remove anything unused. If a dependency was added ahead of a specific
|
|
ticket that hasn't landed yet (e.g. `fs-embed` before
|
|
[028](028-fs-embed-static-bundling.md) wires it in), leave it — this ticket
|
|
is about dead weight, not blocking in-flight work.
|
|
- Re-run the full test suite and a production webapp build after pruning to
|
|
confirm nothing silently depended on a "removed" package.
|
|
|
|
## Acceptance criteria
|
|
|
|
- No dependency remains in either manifest without a corresponding usage in
|
|
the codebase.
|
|
- `cargo test` and the webapp build both pass after pruning.
|
|
|
|
## Depends on
|
|
|
|
None.
|