# NousResearch/hermes-agent · Windows PATH missing Node for npm lifecycle scripts

## Open now

- 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.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #60291. Verify it addresses your case.
- **Recommended:** read PR #60291 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## 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 (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: 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

- #48130: Windows installer detects Node, but npm lifecycle scripts fail with 'node' is not recognized

## Prior & competing PRs

- **#60291: fix(installer): put node.exe on PATH for Windows npm lifecycle scripts**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `scripts/install.ps1`, `tests/test_install_ps1_node_path_for_npm.py`
- **#48155: fix(installer): ensure system Node directory is on PATH for npm lifecycle scripts**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `2bc6e1a74b5848332c606d1b20c97aa7f374947d`, `#60291`

## Fix status

- Merged to main in PR #60291 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-07-07`.
- Subsystem: `apps/bootstrap-installer`