Repository navigation
Have both lite and rich pkgs of PSCore6.x #5681
Description
Activity
I like this. I do have one request: the light weight download cmdlet I've been discussing... I'd like that included in the lite version if possible. The plan is that it wont have any dependency on the web cmdlet code base. But a simple way to download files in native PowerShell would be crucial, IMO, to boot strapping small environments.
Reacted by Steve Lee and Rain Sallow (/u/ta11ow)Mark Kraus (@markekraus) absolutely, the intent of the
litepkg is anything needed to bootstrap the system should be part of it, everything else should be downloaded from PSGalleryNot against the idea but it will need very careful, precise and extensive explanation to the general user otherwise there'll be complaints/comments/statements that all of the functionality has been ripped out of PowerShell. This is analogous to the way the help systems work and we're still seeing comments and complaints about PowerShell not containing any help!
RichardSiddaway agree that it should be clear to users of the
liteversion what they are getting. Ideally, therichversion is simply getting a single module from PSGallery that is a meta-module that just depends on all the other modules. This way it also allows aliteuser to get parity withrichwhich is then just preinstalled.RichardSiddaway I agree with you especially since
Update-Helpis still not working properly. I just tried on a Win10 VM in Azure with the latest updates and even running it as an admin I get:C:\WINDOWS\system32> Update-Help Update-Help : Failed to update Help for the module(s) 'PrintManagement' with UI culture(s) {en-US} : Unable to connect to Help content. The server on which Help content is stored might not be available. Verify that the server is available, or wait until the server is back online, and then try the command again. At line:1 char:1 + Update-Help + ~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (:) [Update-Help], Exception + FullyQualifiedErrorId : UnableToConnect,Microsoft.PowerShell.Commands.UpdateHelpCommand
Steve Lee (@SteveL-MSFT) : I like your idea but please don't create too many bundles with different versioning of their modules in the future because otherwise we'll endup with versioning hell similar to when .Net Core started with hundreds of NuGet packages.
Christoph Bergmeister (@bergmeister) I'm thinking of literally just the two. In the future, we will likely have one additional package only intended for managed nodes where interactive console isn't needed at all.
Related RFC PowerShell/PowerShell-RFC#153
simlarly the idea behind this would further tie in with #1979 and would require further planning and discussion to make a feasibility but this is something that I do think warrants further engineering time for smaller use cases where you want to start with just the base engine and bolt on features as needed
sorta like the SKU modules in Windows work but without the licensing overheads
3 remaining items
microsoft-github-policy-service commented
on Nov 16, 2023 ContributorThis issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commented
on Nov 16, 2023 ContributorThis issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commented
on Nov 16, 2023 ContributorThis issue has not had any activity in 6 months, if this is a bug please try to reproduce on the latest version of PowerShell and reopen a new issue and reference this issue if this is still a blocker for you.
microsoft-github-policy-service commented
on Nov 23, 2023 ContributorThis issue has been marked as "No Activity" as there has been no activity for 6 months. It has been closed for housekeeping purposes.
- marked Powershell "Lite" for ARM64 Architecture #27555 as a duplicate of this issue
on Jun 5, 2026
For deployments of PSCore6.x it would make sense to have a very lightweight pkg that is essentially: Engine, PkgMgmt, PSGet, and basic cmdlets (like Get-Command, Import-Module, Archive module). This pkg would be mostly used on servers being managed and would
install-modulewhat they need.Another pkg would be for the developer/it-pro which is very rich including everything in
lite, but also modules useful for authoring and debugging scripts/modules: JSON, WebCmdlets, YAML module, Management module, HelpSystem, etc...