PowerShell / PowerShell/PowerShell
`Import-Module` should be able to find modules with semver versioned folders
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 55.5k
- Forks
- 8.5k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 88
Description
Summary of the new feature / enhancement
For example, Import-Module MyModuleName should be able to find:
$env:PSModulePath\MyModuleName\1.0.0-preview.1\MyModuleName.psd1
While we would not yet be able to change PSResourceGet to install modules with this structure due to needing to support down level installs reading from the same folder, we should still add this logic into the engine so that we may one day (even if in five years).
Proposed technical implementation details (optional)
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
Start at the Import-Module entry point and inspect how PSModulePath module folders are discovered. Trace the existing version-folder lookup and determine how semver folders such as 1.0.0-preview.1 should be considered. Done means Import-Module MyModuleName can find the shown MyModuleName.psd1 layout without changing PSResourceGet.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100