Skip to content

fix: sync package-lock.json with package.json (npm ci is broken on main)#598

Open
AndrewDongminYoo wants to merge 1 commit into
nashsu:mainfrom
AndrewDongminYoo:fix/sync-package-lock
Open

fix: sync package-lock.json with package.json (npm ci is broken on main)#598
AndrewDongminYoo wants to merge 1 commit into
nashsu:mainfrom
AndrewDongminYoo:fix/sync-package-lock

Conversation

@AndrewDongminYoo

Copy link
Copy Markdown
Contributor

What

Regenerate package-lock.json so it matches package.json again — npm ci currently fails on main.

Why

On current main (6661b81), a clean install aborts:

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 Missing: @emnapi/core@1.11.2 from lock file
npm error Missing: @emnapi/runtime@1.11.2 from lock file
npm error Invalid: lock file's @emnapi/wasi-threads@1.2.1 does not satisfy @emnapi/wasi-threads@1.2.2

This breaks any fresh clone / CI job that relies on npm ci.

How

npm install --package-lock-only (npm 11) — no manual edits. Besides the missing @emnapi/* entries, npm also normalized a few stale "peer": true flags, which is where the extra churn in the diff comes from.

Testing

  • npm ci — clean install succeeds (root; mcp-server was already in sync).
  • tsc --build clean.
  • Mock test suite: 1709 tests pass.

npm ci fails on main because the lock file drifted from package.json:

- Missing: @emnapi/core@1.11.2
- Missing: @emnapi/runtime@1.11.2
- Invalid: @emnapi/wasi-threads@1.2.1 does not satisfy ^1.2.2

Regenerated with npm install --package-lock-only (npm 11). Verified
npm ci, tsc --build, and the mock test suite all pass afterwards.
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.

1 participant