chore: remove unused package-lock.json files - #9713
Merged
Merged
Conversation
The repository standardizes on Yarn v4 (yarn@4.14.1 via packageManager) and uses yarn.lock for dependency resolution in both root and web/wats. All build scripts, CI tasks, and developer workflows exclusively use Yarn. Why these files can be safely removed: 1. Root package-lock.json was added in bc30fec under the assumption it was needed after the Yarn v4 upgrade, while web/wats/package-lock.json was accidentally committed in 2021 (c936fe5). Neither is consumed by any tool or pipeline. 2. Their presence causes automated dependency tooling (Renovate) to detect npm alongside Yarn and attempt dual lockfile updates. This triggers npm ERESOLVE peer dependency errors (e.g. PR concourse#9561 with Babel 8) and blocks automated dependency updates. Also adds package-lock.json to .gitignore to prevent accidental re-commits.
taylorsilva
added
release/undocumented
taylorsilva
approved these changes
Sep 10, 2026
taylorsilva
left a comment
taylorsilva
left a comment
Member
There was a problem hiding this comment.
Will merge once all checks pass.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The repository standardizes on Yarn v4 (yarn@4.14.1 via packageManager) and uses yarn.lock for dependency resolution in both root and web/wats. All build scripts, CI tasks, and developer workflows exclusively use Yarn.
Why these files can be safely removed:
Also adds package-lock.json to .gitignore to prevent accidental re-commits.
Thanks to @pjurczynski for double checking this for me..