Package lockfile sync check #2120
Draft
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.
Asana Task/Github Issue:
Description
Adds a dedicated script (
scripts/check-lockfile.mjs) to validate thatpackage.jsonfiles (root and all workspaces) are in sync withpackage-lock.json. This script is integrated into thelintcommand and added as an early step in various CI workflows to catch lockfile drift proactively and provide clear error messages, preventing silent lockfile rewrites bynpm install.Testing Steps
npm run check-lockfile(should pass).npm run lint(should pass, including the lockfile check).package.json(e.g.,package.jsonorinjected/package.json).npm run check-lockfileand confirm it fails with a descriptive error.npm installto fix.Checklist
Please tick all that apply: