From 736dc0fd86bf9a8a49fa9373b252139b0ce4d20a Mon Sep 17 00:00:00 2001
From: Ben <ben@nousresearch.com>
Date: Fri, 5 Jun 2026 12:03:09 +1000
Subject: [PATCH] fix(nix): use fetchNpmDeps hash for npmDepsHash, not
 prefetch-npm-deps

The previous fix committed the hash from `prefetch-npm-deps`
(sha256-hgnqc...), but the actual `fetchNpmDeps` FOD (fetcherVersion 2)
that `nix flake check` builds wants sha256-cY+gM... . These two tools
disagree for this lockfile, so the build's npm-deps derivation failed
with a hash mismatch even though `fix-lockfiles --check` reported "ok".

Corrected to the build-verified value. Confirmed `nix build .#tui`,
`.#web`, and `.#desktop` all build cleanly with the new hash.
---
 nix/lib.nix | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/nix/lib.nix b/nix/lib.nix
index 2373f9707..ce1445372 100644
--- a/nix/lib.nix
+++ b/nix/lib.nix
@@ -21,7 +21,7 @@ let
 
   # Single npm deps fetch from the workspace root lockfile.
   # All workspace packages share this derivation.
-  npmDepsHash = "sha256-hgnqcpKRPztHhDEpwC7HJrALuJp9wsrV4+GJ6t6HI2c=";
+  npmDepsHash = "sha256-cY+gM1FnTBjmld/uqt7RsqRtW9uQGs8LGokCcxu7bjQ=";
 
   npmDeps = pkgs.fetchNpmDeps {
     inherit src;