runix VS dream2nix

We see a few tools that do a similar built-on-top-of-Nix approach, so we released a Rust library that makes using the "command line API" in a more type-safe manner: https://github.com/flox/runix

I wasn't aware of npt, thanks! We've also released https://github.com/flox/runix as a library to make it easier to wrap Nix.

(I'm on the flox team) we'd love to support that and it's something we've talked about! We already support auto-generation for some languages like Rust because they have a lockfile (e.g. Cargo.lock), but it's a bit trickier for a requirements.txt. We hope at some point to contribute to/integrate with upstream efforts like dream2nix which have auto-generation as their goal

How about dream2nix? I like to use the nix way, but there are many third nix ways

I'm not 100% sure, but looking at the docs [here](https://nix-community.github.io/dream2nix/subsystems/node.html#granular-pure-default) and the implementation [here](https://github.com/nix-community/dream2nix/tree/main/src/subsystems/nodejs/builders/granular-nodejs) it seems as it builds dependencies separately and symlinks (see `install-deps.py` those into a `node_modules` tree. I don't know much about Yarn's PNP (was doing more backend/devex last few years), but it sounds vaguely similar in that each package should be built once as a separate derivation and then symlinked to a big `node_modules`-as-a-symlink-tree derivation?

How are you building your NodeJS project with Nix right now? Recently I spot a new abstraction, it looks good but I havn't tried it yet: https://github.com/nix-community/dream2nix

dream2nix is a great package, that makes a nix-derivation out of node project with the minimal flake

The DavHau/dream2nix project aims to be a generic solution for this issue by splitting the problem into specific stages, each of which can be configured individually (e.g., changing the level of purity)