Skip to content

ElvishJerricco/nix-purescriptPackages

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

16 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

This is a skeleton for building PureScript projects with Nix.

Advantages of Nix

  • With psc-package, you must use the default package set or create a custom set if you want to override package versions. With Nix, you can add packages from arbitrary sources and override existing packages at will.
  • Builds between different projects share common artifacts.
  • Any external, non-purescript build tools can be depended on reproducibly.
  • Remote binary caches allow your team's libraries to be built once remotely, then made available to the team without anyone having to rebuild it.

TODO:

  • Improve the crap used to get shared builds.

    Currently, this symlinks the output files of all dependencies to trick psc into not rebuilding those source files. Instead, psc should have a mechanism for using precompiled packages, like GHC does. It may make sense to strive for a pscWithPackages mechanism.

  • Figure out how to get local incremental builds for development.

    When I'm using Nix with Haskell, I make it possible to build the code with cabal or stack for the sake of incremental builds during development. This is important because fully rebuilding the project takes a long time by comparison. This improvement goes hand-in-hand with psci support, which this currently does not have.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 3

  •  
  •  
  •