fix(powershell): support pipeline input with Invoke-Expression#8297
Merged
wraithgar merged 1 commit intonpm:latestfrom May 15, 2025
alexsch01:version2
Merged
fix(powershell): support pipeline input with Invoke-Expression#8297wraithgar merged 1 commit intonpm:latestfrom alexsch01:version2
wraithgar merged 1 commit intonpm:latestfrom
alexsch01:version2
Conversation
This was referenced May 15, 2025
Merged
wraithgar
approved these changes
May 15, 2025
Closed
wraithgar
pushed a commit
that referenced
this pull request
Jun 25, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
requires #8318 after
needs this PR first: #8278
fixes the case with Invoke-Expression and pipeline input to work
above syntax ONLY works in PowerShell
OUTPUT
given.....
[package.json]
{ "scripts": { "start": "node script.js" } }[script.js]
manually tested with PowerShell