docs: add contributor windows os non-homedrive usage #606
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
This comment was marked as outdated.
This comment was marked as outdated.
aduh95
reviewed
Jan 27, 2025
Co-authored-by: Antoine du Hamel <duhamelantoine1995@gmail.com>
aduh95
approved these changes
Jan 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Issue
As described in issue Contributor Windows build on non-HOMEDRIVE 'Could not resolve "clipanion"' #598, if the instructions in CONTRIBUTING are followed to clone the repo, install dependencies with Yarn and then build with Yarn, these steps fail if running on a Microsoft Windows operating system and the repo has been cloned to a drive which is not the user's
HOMEDRIVE.Pending the implementation of Yarn feature request [Feature] allow packageLocations in .pnp.cjs to be absolute paths yarnpkg/berry#4030, Yarn Plug'n'Play is not compatible with the above Windows configuration.
The corepack repo is currently configured to use Yarn 4.3.1 and since nodeLinker is unconfigured, it defaults to
nodeLinker: "pnp"for Yarn Plug'n'Play.corepack/package.json
Line 19 in 2a04e7c
Change
Add a recommendation and workaround instructions to CONTRIBUTING for contributors working on Microsoft Windows, related to drive usage.