Open
Conversation
Member
|
@claude Can you double check the packages-lock.json please and verify these are correct and have the same main inclusions from packages.json and that none of the versions selected are at risk or infected? |
Contributor
|
Claude Code is working… I'll analyze this and get back to you. |
Author
|
@Geramy I checked the "Allow edits by maintainers" box, so you can make commits in my branch - it's probably easiest to just delete the lock file and manually recreate it yourself with |
Contributor
|
Claude Code is working… I'll analyze this and get back to you. |
Author
|
It seems like Claude is failing because it's unable to check out branches from forks. |
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
2 participants
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.
npm ci --ignore-scriptsshould always be used instead ofnpm installornpm cinpm cirequires package-lock.json to exist