chore: sync package-lock.json with package.json - #1073
Closed
RUKAYAT-CODER wants to merge 1 commit into
Closed
Conversation
Contributor
⚡ Performance Regression ReportReport not available. |
CI installs with `npm ci`, which requires package-lock.json to be in sync with package.json. Several devDependencies (dependency-cruiser, license-checker) and their transitive dependencies were missing from the lock file, causing npm ci to abort before any checks ran. Regenerate the lock file so it satisfies package.json under both strict and legacy peer resolution, restoring installs across all workflows.
RUKAYAT-CODER
force-pushed
the
chore/sync-package-lock
branch
from
September 8, 2026 10:11
c6f4179 to
add4545
Compare
Contributor
Author
|
Superseded by the combined CI-repair PR (#1075), which carries the correct npm 10 lock file plus the workflow rationalization. Closing in favor of that. |
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.
Restores CI installs across all workflows.
Problem
Every CI job installs with
npm ci --prefer-offline --no-audit --legacy-peer-depsand fails at the install step becausepackage-lock.jsonis out of sync withpackage.json. Several devDependencies declared inpackage.json— includingdependency-cruiser@^18.2.0andlicense-checker@^25.0.1— and their transitive dependencies are missing from the lock file, sonpm ciaborts before any check runs.Fix
Regenerated
package-lock.jsonso it satisfiespackage.json. The change only adds the missing dependency trees (76 packages added, 2 removed); no application dependency versions were intentionally bumped. Verified locally thatnpm ci --prefer-offline --no-audit --legacy-peer-depsnow completes successfully.closes #1072