feat: add support for yarn@v4 link: syntax #293
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
Owner
|
Thanks a lot for this, really appreciate it. I'll take a look when I next work on syncpack 🎉 |
Owner
|
I've sorted the conflicts and this is in the dev branch at ade65308.
Pushed to https://github.com/JamieMason/syncpack/commits/yarn-link-specifier/ and parked for the moment, I'm not ready to take on what this needs yet. |
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.
Description (What)
Yarn @ v4 supports a
link:../path/to/thingsyntax for installing another workspace as a dependency but via a symlink. By definition of this syntax these specifiers are always equal regardless of where they are found in the tree, and always match the local version.Justification (Why)
Without this syntax support there is no way to use
link:syntax without syncpack replacing it with specific version numbers which is then invalid as it results in copy-to-install behavior instead of the desired symlink behaviorHow Can This Be Tested?
This PR has unit tests