chore: Remove dead/unused NuGet packages
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- csharp
- Domain
- build-system
Research direction
Open Directory.Packages.props and compare the listed package versions with the issue’s package table and project-reference grep results. Remove only the nine unused PackageVersion entries, then run dotnet build; done means the entries are gone and the build still succeeds.
Written by the indexing model from the issue text.
Description
What
Remove NuGet packages declared in Directory.Packages.props that have zero project references and zero code usage. Verified by grepping PackageReference Include="<pkg>" across all .csproj/.fsproj files.
Packages to remove
| Package | Version |
|---|---|
MessagePack |
2.5.302 |
KubernetesClient |
19.0.2 |
Riok.Mapperly |
4.2.1 — Generator.Equals already handles equality codegen |
Samboy063.Tomlet |
6.0.0 — second TOML parser; Tomlyn is the one actually used |
TUnit |
0.25.21 — suite runs entirely on xunit.v3 |
Github.Actions.Core |
9.0.0 |
Amazon.Lambda.APIGatewayEvents |
2.7.1 |
Amazon.Lambda.AspNetCoreServer.Hosting |
1.9.0 |
Aspire.Hosting |
13.4.3 — bare meta-package; only Aspire.Hosting.AppHost is referenced |
How
Delete each <PackageVersion> entry from Directory.Packages.props. Run dotnet build to confirm nothing breaks.
Part of the broader ponytail over-engineering audit tracked in #3574.
- Dominant language
- C#
- Stars
- 25
- Forks
- 44
- Avg merge
- 22h 15m
- Merged PRs (30d)
- 162
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.
More from elastic/docs-builder
-
chore needs triage tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
elastic/docs-builder#3567 · 1 comment ·
-
ai-triaged bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
elastic/docs-builder#3045 · 4 comments ·
-
ai-triaged ai:eng-question ai:product-question bug needs triage stale
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
elastic/docs-builder#2397 · 2 comments ·
-
ai-triaged ai:quick-fix ai:writer-question documentation needs triage stale
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
elastic/docs-builder#2006 · 3 comments ·
-
[aw] Detection Runs Openagentic-workflows
Difficulty 1/5 Under an hour Newbie friendliness 5/100
elastic/docs-builder#4154 · 1 comment ·
All issues in elastic/docs-builder
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·