Cairn
NousResearch/hermes-agent

NODE_ENV=production causes devDependencies missing in web build

Cluster 27430 · apps/desktop. 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, 3 issues already closed.
Fix event
No fix has been merged to main. 2 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.

A regression where NODE_ENV=production (injected by the TUI/Hermes) causes npm to skip devDependencies during the web UI build, breaking tools like tsc. Multiple fix attempts address this via different approaches such as unsetting NODE_ENV, forcing --include=dev, or overriding the install environment.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · other 1

  • #17906 fix(web): build web UI with NODE_ENV=development so devDependencies install · done elsewhere → 0678f8f, #18682, #17906, #22187, #65595
  • #64708 fix: keep web build deps installed under NODE_ENV=production · other
Closed issues · 3
  • Closed#27430hermes update fails web UI build when NODE_ENV=production — npm install omits devDependencies
  • Closed#49920Desktop hangs in CONNECTING after update — dashboard build fails silently because Hermes injects NODE_ENV=production, making npm install skip devDependencies
  • Closed#65562Regression: TUI injects NODE_ENV=production → hermes update web UI build fails (tsc not found) on main
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.31: 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
apps/desktop
Closed issues
3
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/27430.json
cluster/27430.md