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.

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

Question: package.lock and yarn.lock both exist #856

Open
docrinehart opened this issue Jul 2, 2019 · 1 comment
Open

Question: package.lock and yarn.lock both exist #856

docrinehart opened this issue Jul 2, 2019 · 1 comment

Comments

@docrinehart
Copy link

@ryanlanciaux Is the intent to support folks using either npm OR yarn? In my experience, we typically dictate one or the other for a project and that is the one you use for the project. I ran into some issues running npm install and I'm wondering if that's because I should have used yarn install.

Could you clarify for me if both are intended to exist or which package manager you'd prefer to keep around?

@docrinehart
Copy link
Author

Update: PR #849 removed the yarn.lock file, but the question stands. Both were being used until that last merge, so I'd like to see what your preference is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant