NousResearch/hermes-agent

Node 25 install and compatibility fixes

Cluster 84359 · dashboard. Data as of

Nothing open on GitHub. Fix merged in #97081 on 28 Aug 2026. Check it covers your case.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #97081. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items address installation failures on Node 25, including issues with engine-strict npm configurations, nanoid compatibility, and related desktop/dashboard build breakage. A Windows-specific npm ci failure on engine-blocked systems is also covered.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #97072 fix(install): Windows installs no longer die at npm ci on an engine-blocked system npm (salvage #82033)

    merged to main

    files: .github/workflows/installer-tests.yml, scripts/install.ps1, scripts/tests/test-install-ps1-node-compatibility.ps1

  • #97081 fix(install): Node 25 installs no longer die at the desktop build (salvage #84397)

    merged to main

    files: apps/desktop/package.json, contributors/emails/[redacted:email], package.json, scripts/install.ps1, scripts/install.sh, tests-js/node-engine-alignment.test.ts, tests/test_engines_satisfiable.py

1 PR closed without merging

From the close comments: merged via another change 1

  • #84397 fix(dashboard): stop Node 25 installs from failing at nanoid · merged via another change → ad4adbb, #97081, #82033, #97072
Closed issues · 1
  • Closed#84359[Bug]: `hermes dashboard` fails on Node 25 after update due to engine-strict and nanoid@6
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.50: 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
dashboard
Merged PRs
#97072, #97081
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
28 Aug 2026

For your agent

The same facts, typed.