fix: sync package-lock.json with package.json (npm ci is broken on main)#598
Open
AndrewDongminYoo wants to merge 1 commit into
Open
fix: sync package-lock.json with package.json (npm ci is broken on main)#598AndrewDongminYoo wants to merge 1 commit into
AndrewDongminYoo wants to merge 1 commit into
Conversation
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.
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
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.
What
Regenerate
package-lock.jsonso it matchespackage.jsonagain —npm cicurrently fails onmain.Why
On current
main(6661b81), a clean install aborts: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": trueflags, which is where the extra churn in the diff comes from.Testing
npm ci— clean install succeeds (root;mcp-serverwas already in sync).tsc --buildclean.