PowerShell information for windows 7#6
Closed
KRChapman wants to merge 1 commit into
Closed
Conversation
Contributor
|
Unsure if this is still necessary since it is ~3 years old. Also, vscode no long supports win7. Closing this + please let me know if this needs any further action. Apologies for the extremely late reply. |
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.
I hope that I can save some one else an entire day of frustration that I had. Every time I tried to yarn install vscode packages to it would stall on vscode-ripgrep with no error. I went through major commits from the vs code repo and discovered the exact commit. https://github.com/microsoft/vscode/commits/44d410567333dfbd9da5eab6f56bb2c83c31412e where trouble started for me.
I found posts from others with my same problem setup and details.
microsoft/vscode#77717
Version 1.3.1 of vscode-ripgrep worked great but not the latetest. After investigating the code and comparing the two I discovered that the latest version was using a powershell script. The file did not seem to close after child_process.exec executed the shell script. I investigated and found this post. nodejs/node#25645
After upgrading to powershell 5.1 the package now works and I wanted to share and update so That it can save some one else this frustration.