PowerShell Core is a cross-platform (Windows, Linux, and macOS) automation and configuration tool/framework.
https://docs.microsoft.com/powershell/| Installer Source| Releases (json) (tab)
PowerShell Core is a cross-platform (Windows, Linux, and macOS) automation and configuration tool/framework.
https://docs.microsoft.com/powershell/| Installer Source| Releases (json) (tab)
To update or switch versions, run webi pwsh@stable
(or @v7.4
, @beta
, etc).
The core benefit of running
pwsh
on Mac or Linux is that you get a way to debug Windows scripts without having to boot up Windows.The core benefit of running
pwsh
on Windows is that it's years ahead of pre-installed version.
For example, if you want to create a curl.exe | powershell
script for Windows
(as we do), it's helpful to be able to do some level of debugging on other
platforms.
These are the files / directories that are created and/or modified with this install:
~/.config/envman/PATH.env
~/.local/opt/pwsh/
~/.local/share/powershell/Modules/
~/.local/opt/pwsh/Modules/
Friends don't let friends PowerShell without pwsh-essentials:
Plus, important information for anyone Getting Started with PowerShell:
Assuming you have vim-ale installed - which is included with
vim-essentials - all you need to do is install the
PSScriptAnalyzer
module.
See the "Lint & Fmt" section below.
VS Code should also automatically recognize and use PSScriptAnalyzer
.
See pwsh-essentials for more info but, in short:
pwsh -Command "Install-Module -Name PSScriptAnalyzer -Scope CurrentUser -AllowClobber"
my_ps1='./my-file.ps1'
pwsh -Command "Invoke-ScriptAnalyzer -Fix -ExcludeRule PSAvoidUsingWriteHost -Path '$my_ps1'"
To fmt:
my_ps1='./my-file.ps1'
my_text="$(
pwsh -Command "Invoke-Formatter -ScriptDefinition (Get-Content -Path '$my_ps1' -Raw)"
)"
printf '%s\n' "${my_text}" > "${my_ps1}"
Note: it is several hundred times faster to lint and fmt from a native
PowerShell script than from invoking pwsh -Command
each time.