NousResearch/hermes-agent
Windows PATH missing Node for npm lifecycle scripts
Cluster 48130 · apps/bootstrap-installer. Data as of
Nothing open on GitHub. Fix merged in #60291 on 7 Jul 2026. Check it covers your case.
The short answer
0open issues
0open PRs
3items grouped
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #60291. 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.
A bug where the Windows installer detects Node but fails to include it on PATH during npm lifecycle scripts, plus related fixes to ensure the correct Node executable is accessible in that context.
Open issues0
Open PRs0
Fixes on record
-
#60291 fix(installer): put node.exe on PATH for Windows npm lifecycle scripts
files:
scripts/install.ps1,tests/test_install_ps1_node_path_for_npm.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#48155 fix(installer): ensure system Node directory is on PATH for npm lifecycle scripts · done elsewhere →
2bc6e1a,#60291
Closed issues · 1
- Closed#48130Windows installer detects Node, but npm lifecycle scripts fail with 'node' is not recognized
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.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
- apps/bootstrap-installer
- Merged PRs
- #60291
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 7 Jul 2026