Skip to content

fix(ci): regenerate package-lock.json so npm ci succeeds - #1611

Open
boluxx123 wants to merge 1 commit into
LabsCrypt:mainfrom
boluxx123:fix/sync-package-lock-npm-ci
Open

boluxx123 wants to merge 1 commit into
LabsCrypt:mainfrom
boluxx123:fix/sync-package-lock-npm-ci

Conversation

@boluxx123

Copy link
Copy Markdown

Problem

main is red because package-lock.json is out of sync with the workspace
manifests, so the Install dependencies step aborts before it installs anything:

npm error code EUSAGE
npm error `npm ci` can only install packages when your package.json and
package-lock.json or npm-shrinkwrap.json are in sync.
npm error Invalid: lock file's vitest@2.1.9 does not satisfy vitest@3.2.7
npm error Invalid: lock file's @vitest/coverage-v8@2.1.9 does not satisfy @vitest/coverage-v8@3.2.7
npm error Invalid: lock file's next@16.2.9 does not satisfy next@16.3.3
npm error Invalid: lock file's @stellar/stellar-sdk@15.1.0 does not satisfy @stellar/stellar-sdk@17.2.1
npm error Invalid: lock file's axios@1.15.0 does not satisfy axios@1.20.0
npm error Missing: @playwright/test@1.63.0 / playwright@1.63.0 from lock file
npm error Missing: @noble/ed25519, @noble/hashes, bignumber.js, eventsource, smol-toml, openapi-typescript, ...

This makes every workflow that installs dependencies fail on main, so unrelated
PRs cannot go green either.

Fix

Regenerated the lock against the current package.json files (root, frontend,
backend) with npm install --package-lock-only. lockfileVersion stays 3.

Verification

  • before: npm ci aborts with the EUSAGE sync error above
  • after: npm ci passes the sync check and installs (no EUSAGE)
  • only package-lock.json changes; no manifests or source files are touched

@boluxx123
boluxx123 force-pushed the fix/sync-package-lock-npm-ci branch from d9acdc3 to f4a8698 Compare October 4, 2026 07:53
@boluxx123
boluxx123 force-pushed the fix/sync-package-lock-npm-ci branch from f4a8698 to 1539caa Compare October 21, 2026 21:00

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants