Clarify when yarn.lock is or isn't updated #884
Merged
Conversation
This file contains 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
|
Deploy preview for yarnpkg ready! Built with commit 2859fad |
|
thanks! this is a good call. Might be good to have a dedicated page on the interaction with the lock file, what do you thin @arcanis ? |
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.
Based on a conversation on this Twitter thread: https://twitter.com/arcanis/status/1063043732356898816
This clarifies the difference between when a bare
yarn installusesyarn.lockand when it updatesyarn.lockI looked into making a change at https://yarnpkg.com/en/docs/installing-dependencies#toc-installing-dependencies but it seemed like that was too much to add for that introductory page. Linking to the
yarn installpage seemed sufficient for folks to dig into more detail and learn about these scenarios.