Bug Description

The hermes-tui derivation (in nix/tui.nix) has a stale npmDepsHash. When building on a clean store, the build fails with:

ERROR: npmDepsHash is out of date

The package-lock.json in src is not the same as the in /nix/store/...-npm-deps.

This is the same class of bug as reported in #15272 (and #15244), but for hermes-tui rather than hermes-web.

Root Cause

In the commit that introduced the regression (merged around 2026-04-24 14:26–14:48 UTC), ui-tui/package-lock.json was updated but the corresponding npmDepsHash in nix/tui.nix was not refreshed.

The stale hash in nix/tui.nix line 7:

hash = "sha256-RU4qSHgJPMyfRSEJDzkG4+MReDZDc6QbTD2wisa5QE0=";

The lockfile it should match corresponds to:

sha256-/lL0IXurF4WlyFYVVwDI0Btcx0uChHdmKQ8ZW3NQf5E=

Steps to Reproduce

On a clean nix store (or any environment without cached hermes-tui artifacts):

nix build github:NousResearch/hermes-agent#tui
# or
nix flake check

Both fail with the hash mismatch error above.

Expected Behavior

hermes-tui builds successfully on main.

Actual Behavior

Build fails during npmConfigHook consistency check between package-lock.json and the prefetched npm deps.

Affected Component

• nix/tui.nix — npmDepsHash value
• ui-tui/package-lock.json — updated without corresponding hash bump

Proposed Fix

Update nix/tui.nix line 7 from:

hash = "sha256-RU4qSHgJPMyfRSEJDzkG4+MReDZDc6QbTD2wisa5QE0=";

to:

hash = "sha256-/lL0IXurF4WlyFYVVwDI0Btcx0uChHdmKQ8ZW3NQf5E=";

This is the same remediation as suggested in #15272 for hermes-web.

Related Issues

• [Bug]: Nix ubuntu check failing on main again due to stale hermes-web npmDepsHash (recurrence of #12965) #15244: hermes-web stale npmDepsHash (same root cause)
• [Bug]: Nix CI broken on main — npmDepsHash is out of date (blocks all PRs) #15272: Nix CI broken — duplicate of [Bug]: Nix ubuntu check failing on main again due to stale hermes-web npmDepsHash (recurrence of #12965) #15244