Prerequisites
Steps to reproduce
When installing a PowerShell module hosted in Github Packages with PSResourceGet on Linux the module gets lowered cased. This breaks the ability to import it the module.
Please see details in these two issues linked. I have been attempting to get traction on this for ~3 months, but the other 2 issues seem to be orphaned.
I am trying to support internal dev teams and engineers on Linux/WSL2 and MacOS and this functionality adds a lot of friction in the ability to migrate away from PowerShellGet.
Asking Sydney Smith (@SydneyhSmith) alerickson Anam Navied (@anamnavi) to please take a look if possible, I would greatly appreciate it.
Expected behavior
> Import-Module ModuleName
The above, should work. It does not, because of the casing issue, PowerShell/PSResourceGet doesn't see it at all.
Actual behavior
No module is found when attempting to import.
Error details
At most if you try to specify the name:
> Import-Module: The specified module 'module name' was not loaded because no valid module file was found in any module directory.
This is because of the casing when installed from Github Packages via PSResourceGet.
Environment data
ModuleType Version PreRelease Name ExportedCommands
---------- ------- ---------- ---- ----------------
Binary 1.3.0 preview1 Microsoft.PowerShell.PSResourceGet {Compress-PSResource, Find-PSResource, Get-InstalledPSResource, Get-PSResourceRepository…}
Name Value
---- -----
PSVersion 7.6.3
PSEdition Core
GitCommitId 7.6.3
OS Arch Linux
Platform Unix
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.4
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
** Note the issue exists in Microsoft.PowerShell.PSResourceGet 1.2.0 as well. I tried the latest preview in the event that it possibly fixed the issue.
Visuals
No response
Prerequisites
Steps to reproduce
When installing a PowerShell module hosted in Github Packages with PSResourceGet on Linux the module gets lowered cased. This breaks the ability to import it the module.
Please see details in these two issues linked. I have been attempting to get traction on this for ~3 months, but the other 2 issues seem to be orphaned.
I am trying to support internal dev teams and engineers on Linux/WSL2 and MacOS and this functionality adds a lot of friction in the ability to migrate away from PowerShellGet.
Asking Sydney Smith (@SydneyhSmith) alerickson Anam Navied (@anamnavi) to please take a look if possible, I would greatly appreciate it.
Expected behavior
Actual behavior
No module is found when attempting to import.Error details
Environment data
Visuals
No response