napalm VS nix-bundle

I created https://github.com/nmattia/napalm/issues/34 and https://github.com/nmattia/naersk/issues/183 to move them to nix-community

Sure. NPM is the easy case because the package-lock.json file can easily be read by Nix and contains hashes for all of the packages. This means that simply be importing the file into Nix you can have a reproducible build. No Nix-specific maintenance required.

In the linked case I use this library to manage that https://github.com/nmattia/napalm (in that example I use master but for production I would pin a version). It simply parses the package-lock.json, downloads the packages and uses npm to build the node_modules folder. It also provides some convenient functions for building packages with "bin" files or just linking node_modules inside a build.

Note that this is more for project development. It doesn't use the "system" packages (intentionally) for Node, it fetches whatever versions you have specified from NPM. Nix will only provide the "native" stuff like Node and NPM themselves and any native libraries.

I admit that there is an element of, "but I chose an obscure and challenging linux variant, waaah why isn't it supported" here, but (a) there's currently no flatpak and (b) when, for goodness sakes, will major linux projects begin packaging for Nix/NixOS as a matter of course?

It's not hard, and the benefits go far outside merely supporting Nix, as e.g. a flake.nix file would allow this project to generate docker images, and appImage images, as basically afterthoughts. (See e.g. https://github.com/matthewbauer/nix-bundle.)

Nix flake support would also provide a perfectly reproducible build environment, which can help clarify dependencies, and thus help the project build achieve idempotence, but I'll save the full shill for some github issue.

In fact, I'm inclined to roll up my shirtsleeves and help make this real.

https://github.com/matthewbauer/nix-bundle perhaps?

Another way to approach this would be to advocate Nix as the build system for Flatpak or AppImage. Don't know what the status is of nix-bundle, but if it is possible to turn a Nix package into an AppImage with little extra work that would be ideal.

Nix itself is more focused on "distribute from this host with nix, to this other host with nix".

Though, here is e.g. https://github.com/matthewbauer/nix-bundle, which is supported as an experimental command in nix 2.4.

I believe this tool does: https://github.com/matthewbauer/nix-bundle

Yes, it's extremely powerful once you truly understand Nix.

There are efforts to improve documentation, but it still is lacking (I think the biggest problem is that Nix is so big, not just the OS but it can be utilized as a build system).

Just with NixOS is not exactly clear how can you for example build your custom image.

I think https://nix.dev/ is approaching the documentation from the right direction.

There are also many pieces that people built that you need to find.

For example some things that I found accidentally:

* https://github.com/matthewbauer/nix-bundle

* https://github.com/cleverca22/not-os

Unfortunately those side projects often have even worse documentation.