Powershell - Windows - Fix resolving commands that do not have an exe file #52
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.
On Windows, the current powershell implementation assumes the command will resolve to a file with an
.exe
extension, but the file may be a.bat
,.ps1
,.cmd
, or other type of executable..exe
extension and prefers that.node
file and it prefers executingnode.exe
when writingnode
. Also, why are Linux and Windows builds in the same directory (see what the comment said)? Perhaps this is too much of a breaking change or I am mistaken here, so let me know.References
Closes #51