# NousResearch/hermes-agent · npm ci lockfile sync issues during update flow

## Open now

- Nothing open on GitHub.

A cluster of bugs and fixes around using \`npm ci\` in the update process, where package-lock.json frequently falls out of sync (particularly around @types/node versions), causing failures. Includes attempted mitigations such as discarding lockfile churn and rebuilding runtime assets.

## TL;DR

- 2 member(s): 0 open issue(s), 2 closed issue(s), 0 open PR(s), 0 merged PR(s), 0 PR(s) closed without merging.
- No fix found: no merged or attempted fix PR is on record for this cluster.
- **Recommended:** if this matches your symptom, consider adding to the existing issue(s) below rather than opening a new one.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`LLM_ONLY`): no structural link between members; the grouping rests entirely on an automated relevance judgement over their text.
- Read the members yourself before treating them as one problem.
- Pairwise link density `0.36`: the share of member 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.

## Closed / duplicate issues

- #44121: \[Bug\]: npm ci fails on clean checkout under npm 11 — lock file @types/node@24.13.1 does not satisfy 24.13.2
- #44198: npm ci fails on update — package-lock.json out of sync with @types/node

## Fix status

- No merged fix on record.
- Subsystem: `hermes_cli`