package-lock.json vs. yarn.lock #822
Description
Is there a reason this repo has both package-lock.json and yarn.lock? I think it would be cleaner to use one and gitignore the other.
Right now there is a @cosmwasm/ts-codegen entry in package-lock.json but this is not a dependency anymore. So I assume package-lock.json is outdated.
Should it be removed?