Conversation
npm ci failed with EUSAGE because node_modules/@img/sharp-wasm32 in package-lock.json depends on @emnapi/runtime@^1.11.3, but the lock only had a nested @emnapi/runtime@1.11.1/@emnapi/core@1.11.1 pair. Regenerate the lock with npm install to add the missing top-level 1.11.3 entries. Introduced by bmad-code-org#2878 (413ef03); that PR's own docs-site CI job failed with this exact error but was merged anyway. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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
npm ciindocs-site/fails withEUSAGEbecausenode_modules/@img/sharp-wasm32inpackage-lock.jsondepends on@emnapi/runtime@^1.11.3, but the lock only has a nested@emnapi/runtime@1.11.1/@emnapi/core@1.11.1pair — no top-level entry satisfies^1.11.3.413ef031). That PR's owndocs-siteCI job failed with this exact error (run 35035665195) but was merged anyway, leavingdev/mainwith a broken lockfile.npm cistep in both.github/workflows/docs.yamland.github/workflows/quality.yaml, and the quality gate documented inAGENTS.md.docs-site/package-lock.jsonvianpm install, which adds the missing top-level@emnapi/runtime@1.11.3/@emnapi/core@1.11.3entries and drops some unreferenced@typescript/typescript-*platform stubs that had no parent dependency in the lockfile.Test plan
npm ciindocs-site/now completes cleanly from the regenerated lockfile (verified in anode:24Linux container, matching CI's node version).npm run buildcompletes successfully (309 pages built, search index generated) in the same Linux container — the build pipeline refuses to run on Windows directly, so it can't be verified natively on this machine.docs.yaml,quality.yaml) green on this PR.🤖 Generated with Claude Code