Cairn
NousResearch/hermes-agent

npm ci vs install lockfile churn fixes

Cluster 4048 · hermes cli. Data as of

1 open item. Fix attempted, not merged.

The short answer

0open issues
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
0 issues and 1 PR.

These issues and pull requests address a recurring problem where npm install was being used instead of npm ci in update and setup flows, causing package-lock.json to be rewritten unnecessarily. Related fixes also address dev dependency stripping when NODE_ENV=production is set.

Open issues0

No open issues.

Open PRs1

  • PR#4114fix(setup): use npm ci instead of npm install in hermes update

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #16048 fix(update): avoid lockfile churn during npm installs · superseded by another PR → #16295
Closed issues · 1
  • Closed#4048[Bug]: `hermes update` runs `npm install` instead of `npm ci`, dirtying package-lock.json after every update
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
hermes cli
Closed issues
1
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/4048.json
cluster/4048.md