Currently we have a yarn.lock and a package-lock.json in the repo. I think we should decide which one to use because having two lock files for the same thing is confusing.
The other approach (although I think that is hard to do consistently) is having both but always keeping them in sync.
Currently we have a
yarn.lock
and apackage-lock.json
in the repo. I think we should decide which one to use because having two lock files for the same thing is confusing.The other approach (although I think that is hard to do consistently) is having both but always keeping them in sync.