A flake-parts Nix module for Haskell development
Go to file
2024-01-12 08:58:05 -05:00
.github/workflows ci: Switch to https://flakestry.dev/publish 2023-10-24 09:55:10 -04:00
.vscode Add dev flake (#179) 2023-07-03 16:56:27 -04:00
dev Add dev flake (#179) 2023-07-03 16:56:27 -04:00
doc Use builtins.traceVerbose for logging (#216) 2024-01-12 08:58:05 -05:00
example docs: community.flake.parts host (#209) 2023-11-28 14:51:50 -05:00
nix Use builtins.traceVerbose for logging (#216) 2024-01-12 08:58:05 -05:00
test Use builtins.traceVerbose for logging (#216) 2024-01-12 08:58:05 -05:00
.envrc Add dev flake (#179) 2023-07-03 16:56:27 -04:00
.gitignore Add dev flake (#179) 2023-07-03 16:56:27 -04:00
CHANGELOG.md Use builtins.traceVerbose for logging (#216) 2024-01-12 08:58:05 -05:00
flake.nix ci: Use nixci 0.2 2023-11-07 15:14:55 -05:00
Jenkinsfile Add dev flake (#179) 2023-07-03 16:56:27 -04:00
LICENSE Initial commit 2022-05-30 09:01:58 -04:00
README.md docs: Describe 'debug' option 2024-01-11 15:42:28 +05:30
rundoc.sh Add emanote run command to docs script 2023-03-14 11:21:11 -04:00
runtest.sh runtest.sh: Re-enable doc build 2023-06-01 18:29:55 +02:00

Harmeless Code of Conduct

haskell-flake - Manage Haskell projects conveniently with Nix

There are several ways to manage Haskell packages using Nix with varying degrees of integration. haskell-flake makes Haskell development, packaging and deployment with Nix flakes a lot simpler than other existing approaches. This project is set up as a modern flake-parts module to integrate easily into other Nix projects and shell development environments in a lightweight and modular way.

To see more background information, guides and best practices, visit https://community.flake.parts/haskell-flake

Caveat: haskell-flake only supports the Haskell package manager Cabal, so your project must have a top-level .cabal file (single package project) or a cabal.project file (multi-package project).

Getting started

The minimal changes to your flake.nix to introduce the haskell-flake and flake-parts modules will look similar to:

# file: flake.nix
{
  inputs = {
    ...
    flake-parts.url = "github:hercules-ci/flake-parts";
    haskell-flake.url = "github:srid/haskell-flake";
  };

  outputs = inputs:
    inputs.flake-parts.lib.mkFlake { inherit inputs; } {
      systems = [ "x86_64-linux", ... ];
      imports = [
        ...
        inputs.haskell-flake.flakeModule
      ];
      perSystem = { self', system, lib, config, pkgs, ... }: {
        haskellProjects.default = {
          # basePackages = pkgs.haskellPackages;

          # Packages to add on top of `basePackages`, e.g. from Hackage
          packages = {
            aeson.source = "1.5.0.0" # Hackage version
          };

          # my-haskell-package development shell configuration
          devShell = {
            hlsCheck.enable = false;
          };

          # What should haskell-flake add to flake outputs?
          autoWire = [ "packages" "apps" "checks" ]; # Wire all but the devShell
        };

        devShells.default = pkgs.mkShell {
          name = "my-haskell-package custom development shell";
          inputsFrom = [
            ...
            config.haskellProjects.default.outputs.devShell
          ];
          nativeBuildInputs = with pkgs; [
            # other development tools.
          ];
        };
      };
    };
}

haskell-flake scans your folder automatically for a .cabal or cabal.project file. In this example an imaginary my-haskell-package.cabal project is used.

To see in more detail how to use haskell-flake in a realistic Haskell project with several other development tools, take a look at the corresponding Haskell single-package project Nix template and this Haskell multi-package project Nix example.

Documentation

https://community.flake.parts/haskell-flake

Discussion

Zulip is the primary venue for discussion; we also have Github Discussions enabled.