NousResearch/hermes-agent
Skip npm install during update when lockfile unchanged
Cluster 17268 · hermes cli. Data as of
Nothing open on GitHub. Fix attempted, not merged.
The short answer
0open issues
0open PRs
5items grouped
- Known?
- Yes. 5 related items grouped here, 2 issues already closed.
- Fix event
- No fix has been merged to main. 3 PRs closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese members all concern the update command running Node.js dependency installation (npm ci/install) every time, including a report of roughly 8 minutes spent on Windows. The pull requests and feature requests propose skipping that step when lockfiles or node_modules already match.
Open issues0
Open PRs0
3 PRs closed without merging
From the close comments: superseded by another PR 2 · stale or abandoned 1
- #17386 feat(update): skip npm ci when node_modules already matches lockfile (#17268) · stale or abandoned
- #39397 perf(cli): skip npm install during update when lockfile is unchanged (#17268) · superseded by another PR
-
#43875 fix(update): skip npm ci when lockfiles haven't changed · superseded by another PR →
#39397
Closed issues · 2
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.44: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- hermes cli
- Closed issues
- 2
- Attempts
- 3 PRs closed without merging