Switch cwd arguments to build commands to use fsPath
#545
Conversation
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
stefanvanburen
changed the title
cwd arguments to build commands to use fsPath
Member
Author
|
@doriable maybe you have an actual windows PC to test this on? 😅 |
Closed
No more `uri.path` usage.
doriable
approved these changes
Jan 23, 2026
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 think using
.pathfor these is causing the issues we're seeing in #522 with being unable to run these commands on windows, as we're passing in aslash/separated/pathfor thecwd, resulting in ENOENTs.We originally reworked these commands in #407, for reference.
Fixes #522.