You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
nix: node_modules hash mismatch and bun version constraint too strict for some nixpkgs-unstable snapshots #27
When building from nixpkgs-unstable where bun is at 1.3.13 (vs the expected ^1.3.14 in the project),
the node_modules derivation produces a different hash than the one locked in nix/hashes.json.
Error:
hash mismatch in fixed-output derivation:
specified: sha256-OttgLsPJSYW1b9RGqiYSi7qPdDC3GuD2FE7k5tPe6Iw=
got: sha256-vB4imi5LtCxnDuOaJFQh+asK51RUDCnIVCkIzBQN12o=
Problem 2: bun version check too strict
The build script in packages/script/src/index.ts requires bun@^1.3.14,
but the current nixpkgs-unstable ships bun 1.3.13, causing the build to fail:
error: This script requires bun@^1.3.14, but you are using bun@1.3.13
Workaround
I forked the repo and:
Updated nix/hashes.jsonx86_64-linux hash to the got value
Added a patchPhase in nix/deepagent-code.nix to relax the bun version check to ^1.3.13
Suggestion
The hashes.json approach is fragile because it pins a hash tied to a specific
nixpkgs snapshot. Consider either:
Using a hash derivation approach that tolerates minor bun version differences
Activity
fix(nix): update node_modules hash and use build-time bun version for…