-
Notifications
You must be signed in to change notification settings - Fork 31
yarn.lock vs. package-lock.json #75
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
Comments
I think we're using https://github.com/angular/clang-format/blob/master/.github/workflows/node.js.yml Care to send a PR to update the docs and delete yarn.lock? |
yarn.lock is older than package-lock.json. Fixes: angular#75
No change to the docs. It turns out that the mentions of |
yarn.lock is older than package-lock.json. Fixes: #75
Thanks for the fix @Trott ! |
This has two competing lock files. Which one is the one to use? README seems to suggest that it's yarn.lock but it's 3 months older than the package-lock.json, so that suggests that maybe the package-lock.json is the one to use?
The text was updated successfully, but these errors were encountered: