Should I commit yarn.lock and package-lock.json files?

Question

We\'re using yarn for all our deterministic pkg installations but don\'t prevent the user from using npm - I\'m guessing having both these files will cause issues however. S

Answer 1

These files are managed by your tools, so–assuming using yarn will effectively update the package-lock.json–I suppose committing both files works fine.

I think the most important for your user is package-lock.json (I, for instance, don't use yarn) so this one has to be committed.

For the yarn.lock, it depends if you work alone or in a team. If solo, then I suppose there is no need to commit it. If you (plan to) work in a team, then you probably should commit it, at least until yarn supports it