NuGet/Home

[Feature]: Make dotnet list package work without restore when using lock files

Open

#11,770 opened on Apr 22, 2022

View on GitHub
 (9 comments) (1 reaction) (0 assignees)HTML (292 forks)batch import
Area:RestoreRepeatableBuildFunctionality:ListPackagePriority:3Product:dotnet.exeType:Featurehelp wanted

Repository metrics

Stars
 (1,459 stars)
PR merge metrics
 (Avg merge 464d 23h) (1 merged PR in 30d)

Description

NuGet Product(s) Involved

dotnet.exe

The Elevator Pitch

(Was asked to post this here instead of https://github.com/dotnet/sdk/issues/24194)

We are running dotnet list package (with --vulnerable, --outdated, and --deprecated) in a CI pipeline. This seems to require restoring the projects first. This adds overhead in the pipeline, which seems unnecessary since we use lock files (packages.lock.json) which AFAIK contains all necessary information. I propose allowing dotnet list package to work with the information in lock files, without needing a restore.

Additional Context and Details

No response

Contributor guide

Research direction
Investigate how 'dotnet list package' currently depends on the restore process and explore leveraging lock files (packages.lock.json) to extract package information without performing a full restore. Review the NuGet source code for list command and restore flow.
Tech stack
csharp
Domain
clibackendbuild system
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
.NETNuGetCI/CD
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40