It probably wouldn't be that hard to package. For example, I committed this to a fork of a C++ package a few days ago just to be able to build it in Nix; it on

It probably wouldn't be that hard to package. For example, I committed this to a fork of a C++ package a few days ago just to be able to build it in Nix; it only took me like 20 minutes to figure out. It's literally just 1 step away to go from building it here to putting this in nixpkgs but I don't want to be responsible for it (I've also never taken that step yet) and it also doesn't (yet) use Flakes: https://github.com/10gic/vanitygen-plusplus/blob/master/default.nix https://github.com/10gic/vanitygen-plusplus/blob/master/defa... Note that I am not a C++ developer, I just know the basics. In theory, though, you'd just have to find a similar Node example out there and crib off its nix config/build file. And if you converted it to a flake, you'd have a guaranteed-reproducible build (but then you'd also be responsible for updating it). Perhaps that's why nixpkgs has one of the highest package counts in the Linux space of package managers. It's pretty nice.