efcf01325b
Since the formatter always depended on devShell packages, building the formatter involved building all the devShell packages, which can be slow. In the case where formatters are set to plain strings, such as "nixpkgs-fmt", depending on the devShell packages is necessary in order to put the formatting utility on the path. But when a formatters option is set to an package, such as "${pkgs.nixpkgs-fmt}/bin/nixpkgs-fmt", then that formatter option does not depend on the devShell packages. Flakelight now detects if any of the configured formatters are using the first form, and only if so does it add the devShell packages dependency. This allows the first form to still work, without incurring a cost for flakes that only use the second form. Users can use the second form for all formatters options if they wish to not build the devShell packages when using the formatter. |
||
---|---|---|
.github/workflows | ||
builtinModules | ||
misc | ||
nix/flakelightModules | ||
templates | ||
tests | ||
.editorconfig | ||
.envrc | ||
.gitignore | ||
API_GUIDE.md | ||
default.nix | ||
flake.lock | ||
flake.nix | ||
LICENSE | ||
README.md |
Flakelight
A modular Nix flake framework for simplifying flake definitions.
Goals
- Minimize boilerplate needed for flakes
- Support straightforward configuration of all vanilla flake attributes
- Allow sharing common configuration using modules
- What can be done automatically, should be
- Provide good defaults, but let them be changed/disabled
Features
- Handles generating per-system attributes
- Extensible using the module system
- Given package definitions, generates package and overlay outputs
- Automatically import attributes from nix files in a directory (default
./nix
) - Builds formatter outputs that can format multiple file types
- Provides outputs/perSystem options for easy migration
Documentation
See the API docs for available options and example usage.
Additional modules
The following modules are also available:
Examples
Shell
The following is an example flake.nix for a devshell, using the passed in
nixpkgs. It outputs devShell.${system}.default
attributes for each configured
system. systems
can be set to change configured systems from the default.
{
inputs.flakelight.url = "github:nix-community/flakelight";
outputs = { flakelight, ... }:
flakelight ./. {
devShell.packages = pkgs: [ pkgs.hello pkgs.coreutils ];
};
}
With this flake, calling nix develop
will make hello
and coreutils
available.
To use a different nixpkgs, you can instead use:
{
inputs = {
nixpkgs.url = "nixpkgs/nixpkgs-unstable";
flakelight.url = "github:nix-community/flakelight";
};
outputs = { flakelight, ... }@inputs:
flakelight ./. {
inherit inputs;
devShell.packages = pkgs: [ pkgs.hello pkgs.coreutils ];
};
}
Rust package
The following is an example flake for a Rust project using flakelight-rust
,
invoked by using flakelight-rust
's wrapper.
Package metadata is taken from the project's Cargo.toml
.
{
inputs.flakelight-rust.url = "github:accelbread/flakelight-rust";
outputs = { flakelight-rust, ... }: flakelight-rust ./. { };
}
The above flake exports the following:
- Per-system attributes for default systems (
x86_64-linux
andaarch64-linux
) packages.${system}.default
attributes for each systemoverlays.default
providing an overlay with the package (built with the applied pkg set's dependencies)devShells.${system}.default
that providesrust-analyzer
,cargo
,clippy
,rustc
, andrustfmt
as well as setsRUST_SRC_PATH
checks.${system}.${check}
attributes for build, test, clippy, and formatting checksformatter.${system}
with additional support for formatting Rust files
Equivalently, you can just import the flakelight-rust
module as follows:
{
inputs = {
flakelight.url = "github:nix-community/flakelight";
flakelight-rust.url = "github:accelbread/flakelight-rust";
};
outputs = { flakelight, flakelight-rust, ... }: flakelight ./. {
imports = [ flakelight-rust.flakelightModules.default ];
};
}
See flakelight-rust.nix to see how you could configure it without the module.
C application
The following example flake is for a C project with a simple make
setup.
{
description = "My C application.";
inputs.flakelight.url = "github:nix-community/flakelight";
outputs = { flakelight, ... }:
flakelight ./. {
license = "AGPL-3.0-or-later";
package = { stdenv, defaultMeta }:
stdenv.mkDerivation {
name = "hello-world";
src = ./.;
installPhase = ''
runHook preInstall
make DESTDIR=$out install
runHook postInstall
'';
meta = defaultMeta;
};
devShell.packages = pkgs: with pkgs; [ clang-tools coreutils ];
formatters = {
"*.h" = "clang-format -i";
"*.c" = "clang-format -i";
}
};
}
This flake exports the following:
- Per-system attributes for default systems (
x86_64-linux
andaarch64-linux
) packages.${system}.default
attributes for each system, with license and description setoverlays.default
providing an overlay with the package (built with the applied pkg set's dependencies)devShells.${system}.default
that providesclang-tools
andcoreutils
checks.${system}.${check}
attributes for build and formatting checks.formatter.${system}
with additional support for formattingc
andh
files withclang-format
C application using autoloads
The above example can instead use the autoload directory feature for the package like the following. Most attributes can be autoloaded.
./flake.nix
:
{
description = "My C application.";
inputs.flakelight.url = "github:nix-community/flakelight";
outputs = { flakelight, ... }@inputs:
flakelight ./. {
license = "AGPL-3.0-or-later";
devShell.packages = pkgs: with pkgs; [ clang-tools coreutils ];
formatters = {
"*.h" = "clang-format -i";
"*.c" = "clang-format -i";
}
};
}
./nix/packages/_default.nix
:
{ stdenv, defaultMeta }:
stdenv.mkDerivation {
name = "hello-world";
src = ./.;
installPhase = ''
runHook preInstall
make DESTDIR=$out install
runHook postInstall
'';
meta = defaultMeta;
}
A leading underscore in filename is stripped (default needs to be escaped to not conflict with dir import).