fix: regenerate package-lock.json to resolve npm ci failures#115
Merged
Conversation
The committed lockfile was out of sync with client/package.json: it pinned vite@8.0.5 while the client requires ^8.0.10 (npm flagged it 'invalid'), so 'npm ci' failed with EUSAGE on main and on every Dependabot PR branched from it — blocking all of CI. Regenerated from a clean install so the lockfile matches the manifests; npm ci now succeeds and the build passes.
atomantic
force-pushed
the
fix/lockfile-sync
branch
from
b264cec to
ecba637
Compare
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.
Summary
The committed
package-lock.jsonwas out of sync withclient/package.json: it pinnedvite@8.0.5while the client requires^8.0.10(npm flagged itinvalid). As a resultnpm cifailed withEUSAGE("can only install packages when package.json and package-lock.json are in sync") onmainand on every open Dependabot PR branched from it — which is why all their CI builds were red.Regenerated the lockfile from a clean install so it matches the manifests.
Test plan
npm ci— succeeds (was failing on main).npm run build— passes, 0 TS errors.