A version of MyInvocation.Statement without redirect operators

[alexsch01]

Summary of the new feature / enhancement

As someone who was working on powershell PRs for npm (I don't represent them),

I found out that $MyInvocation.Statement (and the Internal equivalent in Windows PowerShell) in pwsh doesn't strip out the redirect operators

So like the following

npm -v > hello.txt

doesn't turn into

npm -v

currently, would be nice if there existed a variable that gave the stripped output

Proposed technical implementation details (optional)

No response

[mklement0]

The relevant working group will have to decide whether such a feature is of enough general interest.

In the meantime, you can implement this yourself with the help of the PowerShell SDK:

$statementWithoutRedirections = 
   [Management.Automation.Language.Parser]::ParseInput($MyInvocation.Statement, [ref] $null, [ref] $null).
   EndBlock.Statements.PipelineElements.CommandElements.Extent.Text -join ' '

# Sample output
[pscustomobject] @{
  Statement = $MyInvocation.Statement
  StatementWithoutRedirections = $statementWithoutRedirections
}

Note that, as with the original .Statement property value, you'll get (part of) the command line as submitted, i.e. without variable references such as $HOME or (sub)expressions having been expanded.

[alexsch01]

$statementWithoutRedirections =
[Management.Automation.Language.Parser]::ParseInput($MyInvocation.Statement, [ref] $null, [ref] $null).
EndBlock.Statements.PipelineElements.CommandElements.Extent.Text -join ' '

@mklement0 thank you, that dramatically reduced code complexity

[microsoft-github-policy-service]

📣 Hey @@alexsch01, how did we do? We would love to hear your feedback with the link below! 🗣️

🔗 https://aka.ms/PSRepoFeedback

Microsoft Forms

[alexsch01]

Used the help from this to make npm/cli#8318 into npm 11.3.0 / nodejs 24.3.0!