fix: sync package-lock metadata with package.json - #131
Open
sergiomaldo wants to merge 1 commit into
Open
Conversation
package-lock.json recorded version 0.0.1 while package.json is at 0.6.2, and carried no license field. Any 'npm install' silently rewrites both, leaving a modified lockfile in the worktree on a fresh clone. That dirty file is easy to stage by accident into an unrelated pull request. Sync the metadata. This touches only the version and license fields; no dependency is added, removed, or re-resolved.
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.
package-lock.jsonrecords"version": "0.0.1"whilepackage.jsonis at0.6.2, andthe lockfile's root package entry carries no
licensefield.Any
npm installsilently rewrites both, so a fresh clone ends up with a modifiedlockfile in the worktree before any work has been done. That dirty file is easy to stage
by accident into an unrelated pull request.
Changes
Sync the metadata by running
npm install --package-lock-only. This touches only theversionandlicensefields — 3 insertions, 2 deletions. No dependency is added,removed, or re-resolved.
Verified idempotent: a second
npm install --package-lock-onlyafter this changeproduces no further diff.
🤖 Generated with Claude Code
https://claude.ai/code/session_01SMqm8tGT3ksTtYgqPao6kF