@PacoVelobs unfortunately not! Bun's binary lock file makes it so we can't parse it in Nix and fetch dependencies. The best solution I have managed to find is to convert the bun lock file to yarn.lock and then build with that. Sometimes that doesn't work and I needed to then convert the yarn lock file to package-lock.json and use buildNpmPackage. But sometimes that doesn't work and it turns out bun doesn't include hashes for transients if you have any dev dependencies.
@PacoVelobs if you are okay with IFD then you could perform that conversion in Nix, leaving you with only the bun lock file to track in your repo. Still not ideal, but it at least works.
@jakehamilton
Thanks a lot for both the answer and then rational behind it
@PacoVelobs it is a difficult one! Happy to help :)
Bun has an issue open on their roadmap for replacing the binary lock file with a text one. It has been pushed out once already, but hopefully it will be worked on soon!