Repository navigation
Import-Module should be able to find modules with semver versioned folders #21371
Description
Activity
Related issue: #2983
Once the engine has support for this feature PSResourceGet should have logic to enable prerelease folders while leaving earlier versions with the existing behavior.
Once the engine has support for this feature PSResourceGet should have logic to enable prerelease folders while leaving earlier versions with the existing behavior.
There's a lot more risk associated with that as it would break folks trying who use multiple versions. This issue is just about a potential engine change that may open up a road for that in the future.
Will this suffice for nuget versioned packages though? Like
1.2.3.4-preview.1? Cause that's valid in the PSGallery, right? And PSResourceGet usesNugGet.Versioning.Will this suffice for nuget versioned packages though? Like
1.2.3.4-preview.1? Cause that's valid in the PSGallery, right? And PSResourceGet usesNugGet.Versioning.The intent would be to mirror the versions that PSRG supports yeah. The idea would be to add only the most minimal implementation we can so that in the future when the oldest LTS also happens to be able to load modules like this, we would be able to actually consider making the transition.
This issue is more of a placeholder until I can find the spare time to write a full proposal
Summary of the new feature / enhancement
For example,
Import-Module MyModuleNameshould be able to find:$env:PSModulePath\MyModuleName\1.0.0-preview.1\MyModuleName.psd1While we would not yet be able to change
PSResourceGetto 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