Repository navigation
fix(deps): regenerate package-lock.json to resolve npm ci EUSAGE - #55
Merged
Merged
Conversation
Codesmith's lockfile-removal PR (#54) hand-trimmed package-lock.json when it dropped @semantic-release/changelog + @semantic-release/git, instead of running a real npm install -- left stale transitive sub-versions behind. npm ci then fails EUSAGE: package.json and package-lock.json are no longer structurally in sync. Regenerated via npm install --package-lock-only against the current package.json (no dependency version changes, lockfile only). Verified: npm ci clean, build clean, tests pass. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
|
🎉 This PR is included in version 1.0.5 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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.
Why
npm cihas been failing fleet-wide on this repo's Dependabot dev-deps branches since 2026-10-07 22:4xZ:package.jsonandpackage-lock.jsonare no longer in sync (EUSAGE, missing transitive packages).Root cause: lockfile desync introduced by Codesmith PR #54 -- it removed
@semantic-release/changelog+@semantic-release/gitfrom both files, but thepackage-lock.jsonedit was a pure deletion diff (no realnpm installrun), leaving stale transitive sub-versions behind. If Codesmith re-touches this repo, the lockfile must be regenerated vianpm install, not hand-trimmed.Same fix as the canary, WYRE-AI/node-huntress#48.
What
Regenerated
package-lock.jsonvianpm install --package-lock-onlyagainst the current (unchanged)package.json. No dependency version ranges changed -- lockfile only.Tests
npm ci,npm run build,npm testall pass locally.🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.