Add fail-fast package-lock.json sync check#8
Merged
DhavalGojiya merged 1 commit intomainfrom Sep 16, 2025
Merged
Conversation
- Introduce `package-lock-utd` package to verify lockfile is up-to-date - Add CI step to run this check before build/lint steps - Ensures pipeline fails immediately if lockfile is out-of-sync
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
1 participant
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.
📦 Lockfile Sync Check in CI
This PR adds a fail-fast check for package-lock.json in the CI pipeline to ensure it is always up-to-date with
package.json✅ What this PR does
package-lock-utdcheck usingnpx --yes [email protected]to verify lockfile is in sync🖼 Example Failure
If the lockfile is not in sync, the CI will fail like this:
This ensures developers cannot merge changes that break the lockfile, keeping dependencies consistent across all environments.