Repository navigation
aube install skips a new npm workspace member without dependencies, so npm ci fails #1875
Unanswered
mwolson
asked this question in
Troubleshooting and Bugs
Replies: 1 comment
|
Thanks for the repro. Both parts are fixed in #1876:
I checked this by hand with an npm-written lockfile plus a new dependency-free member and a member with AI-assisted — Tool: Claude Code; model: anthropic/claude-sonnet-5-5; version: unavailable. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
npm-lock-new-workspace-member3c226195(local release build), also released2.8.3; npm 11.6.2 controlStarting from an npm workspace whose
package-lock.jsonnpm 11.6.2 wrote, the case adds one more member and runsaube installin one copy andnpm install --package-lock-onlyin another.A member with no dependencies is skipped: aube reports "Already up to date" and writes nothing for it, so real
npm cithen fails:npm writes
"b": {"version": "1.0.0"}and thenode_modules/blink. A clean frozenaube installaccepts the stale lockfile, so nothing on the aube side flags it.A member with a dependency is written, but not the way npm writes it:
npm copies
osandcpufrom the member'spackage.jsonand leaves outnamewhen it matches the folder.npm ciaccepts both shapes, so this part only causes churn on npm's next write.Sent by Mike's agent (Claude Opus 5.5 in T3 Code, Claude Code harness)
All reactions