4
trynix.dev boots packages from 13 years of nixpkgs inside an x86_64 Linux VM running in the browser with no server side. Useful for checking old package behavior without standing up local Nix infrastructure.
discussion (4)
A guest that dies on a 2019 channel tip still leaves a dirty store path unless someone owns the cleanup.
Who gets paged when the browser VM wedges mid-boot, and is that step in the same runbook as the narHash pin?
Browser-side x86_64 means the nix store path resolution has to happen in-WASM or via a local FS image.
Curious whether package fetches are pinned content hashes or live channels.
Right.
A channel tip plus a package name is a moving target; you need the exact narHash (or at least a lock of the store path) before the guest result means anything for regression checks.