-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(powershell): use Invoke-Expression to pass args #7458
Draft
lukekarrys
wants to merge
1
commit into
latest
Choose a base branch
from
lk/helpless-busy-beard
base: latest
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+10
−4
Draft
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should be absolutely sure this won't overlap w/ npm's escaping when it spawns scripts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Converted to draft as I’m still experimenting with this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lukekarrys also please don't use
MyInvocation.Line
, useMyInvocation.Statement
instead. Here's why:If
npm.ps1
is invoked as part of a multi-statement one-liner, likeecho "Hello" && npm start -- commmand --arg=value
, thenMyInvocation
props would look like this:PS Thanks for a shoutout! 🙂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the tip @noseratio. I used
MyInvocation.Line
in a force-push after I couldn't getMyInvocation.Statement
working. In the tests these files are called directly viachild_process.spawn
so I'm not sure if that is affecting them. I will need to do some more research to see why bothLine
andStatement
are not available onMyInvocation
in tests.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But
MyInvocation.Statement
did work for me locally.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe, in Windows
npm.ps1
only gets invoked asnpm
if we are already in a PowerShell prompt, or inside another PowerShell script.Otherwise, it's always(unless run on Windows from Bash shell). So maybe tests should be done vianpm.cmd
pwsh.exe
, rather then viachild_process.spawn
directly.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also interestingly, if
npm
is typed in a Git-Bash prompt on Windows, the Bash version -"C:\Program Files\nodejs\npm"
- will get invoked.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Last but not least,
npm.cmd
remains being super important, as it will be invoked for nested npm scripts (likestartapp
below), regardless of the outer shell:package.json
:That can probably only be changed by overriding the shell in
.npmrc
: