Ignore package-lock.json and yarn.lock
jieyouxu opened this issue · 1 comments
jieyouxu commented
It looks like contributors might be using different tooling (yarn vs npm) which generate different lockfiles respectively.
Keep only one of the lock files and specify which package manager to use, or else you likely will get different build results depending on which package manager you are using.
Since this is a website and not a CLI tool or binary, you do not need to include the package lock files anyways.
Consider ignoring both package-lock.json and yarn.lock.