microsoft / microsoft/winget-cli
WinGet supports installing PowerShell modules as a portable application
Open
Nobody has claimed this yet.
Issue-Feature
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Description of the new feature / enhancement
I want to be able to install PowerShell modules from an archive using WinGet. I'd like installed modules to be available in all versions of PowerShell with which they are compatible. I'd like to be able to specify to install in either the user scope or machine scope.
Proposed technical implementation details
No response
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
The issue names no files, tests, or entry points. Start by surveying WinGet's package installation flow and PowerShell module handling, including how user and machine scopes are represented; done means defining and implementing archive-based module installation across compatible PowerShell versions with both requested scopes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100