For Windows PowerShell/PowerShell Core modules to have a clear cross-compatibility story, we need PowerShell Core to respect the CompatiblePSEditions field.
This means, for PowerShell Core:
Get-Module -ListAvailable lists only those modules on the module path that are Core compatibleImport-Module will only import a module that is Core compatible and throw an error otherwise- The absence of the
CompatiblePSEditions field should imply a sane default. The current suggested default is CompatiblePSEditions = @('Desktop'), i.e. compatible with Windows PowerShell (since there is no such field in Windows PowerShell and modules written for it only would lack this field by default).
For Windows PowerShell/PowerShell Core modules to have a clear cross-compatibility story, we need PowerShell Core to respect the
CompatiblePSEditionsfield.This means, for PowerShell Core:
Get-Module -ListAvailablelists only those modules on the module path that are Core compatibleImport-Modulewill only import a module that is Core compatible and throw an error otherwiseCompatiblePSEditionsfield should imply a sane default. The current suggested default isCompatiblePSEditions = @('Desktop'), i.e. compatible with Windows PowerShell (since there is no such field in Windows PowerShell and modules written for it only would lack this field by default).