Archit Gupta

Hey, thanks for reaching out! As for the proposal, I'd be interested in what use cases this enables or makes cleaner or more performant (though that should probably go in...

Letting something like `nix build nixpkgs --recipe ./recipe.nix` work would be cool too, and easily allow an arbitrary file with one of these definitions to be build with inputs from...

One thing that would be of great benefit from the lang side would be to be able to distinguish a package definition from a function that takes the package set....

Rather than a workaround, that is intended behavior. Unless inputs is passed to flakelight, it can't get the defaults otherwise, which is why with other libraries, passing inputs is required....

For config repos where messing with Nix stuff is the point, I find `--override-input` occasionally useful for testing unreleased input versions, but most of the flakes I write are one-offs...

Added a note to the docs. Will also add some templates.

Sorry for delay; have been busy. The `inputs'` arg is provided by flakelight, so is not available in second flake. The args to modules come from the `nixosSystem` as well,...

if you change vm2 to not call nixosSystem explicitly, it will work: ```nix nixosConfigurations.vm2 = { inherit system; modules = [ self.nixosModules.default ]; }; ``` If you don't call it,...

Yeah the problem with that approach is that the parameters are no longer named, and the parameter names affect how modules are passed args. A module with `{ ... }@args`...

You'll also need to filter out inputs, so that if their nixpkgs modules don't have an inputs arg it would still work, like follows: ```nix nixosModules.wrapped = let f =...