Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Do we put .lock file under version control? #53

Closed
RJ722 opened this issue May 26, 2018 · 2 comments
Closed

Do we put .lock file under version control? #53

RJ722 opened this issue May 26, 2018 · 2 comments

Comments

@RJ722
Copy link
Member

RJ722 commented May 26, 2018

Is it a good idea to keep the .lock file under version control? Also, we are getting a conflict in #52
@iamareebjamal
Copy link
Contributor

Yes we do

@RJ722 RJ722 closed this as completed May 26, 2018
@mohdomama
Copy link
Member

@RJ722

The package.json describes the intended versions desired by the original author, while yarn.lock describes the last-known-good configuration for a given application.

yarnpkg/yarn#838 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@iamareebjamal @RJ722 @mohdomama