Mention yarn linking in contributing guide to run local npm packages #43745
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
Unlike Ruby gems, Node packages can use multiple versions of the same package. Linking is needed to tell Node to use the same local package for all instances of a dependency. [skip ci]
gmcgibbon
force-pushed
the
yarn_link_contributing_guide
branch
from
6528896 to
a981911
Compare
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.
Summary
In #43667, there was some confusion about how to use unreleased changes to npm packages. I think this should be documented because it isn't straightforward. Unlike Ruby gems, Node packages can use multiple versions of the same package. Linking is needed to tell Node to use the same local package for all instances of a dependency.