PowerShell / PowerShell/PSResourceGet
Local cache for `.nupkg` like other package managers
Open
Nobody has claimed this yet.
Area-PSRepository
feature_request
- Dominant language
- C#
- Stars
- 576
- Forks
- 114
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
Summary of the new feature / enhancement
It could be useful with a local cache of downloaded .nupkg files, like other package managers does.
- Bun: https://bun.com/docs/pm/global-cache
- Chocolatey: https://docs.chocolatey.org/en-us/choco/commands/cache/
- Scoop: https://github.com/ScoopInstaller/Scoop/blob/master/libexec/scoop-cache.ps1
Having this would make it feasible to implement other fatures too, like:
Proposed technical implementation details (optional)
- Make it optional.
- Make cache invalidation / deletion / purge logic configurable.
- Keep to latest version of each script/module?
- Delete cached items after x days?
- Could help with cache in CI/CD too, like in GitHub actions, if
Install-Packagedid not delete the.nupkgfiles it downloaded. - Add some cmdlets to manage cache
- Get current cached items and total size.
- Clear cache.
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 proposed local .nupkg cache behavior and the linked PSResourceGet issue 1646. Compare the referenced Bun, Chocolatey, and Scoop cache approaches, then define the optional caching, invalidation, purge, CI/CD behavior, and cache-management cmdlets needed for a complete design.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100