Automatic (re)compilation of Purescript code
Latest commit 1489737 Nov 30, 2016 @adinapoli committed on GitHub Merge pull request #22 from filib/issue-21
Issue 21
Failed to load latest commit information.
.travis.yml Compile the examples as well Apr 20, 2016
LICENSE Initial work Apr 21, 2016
snaplet-purescript.cabal Fix modules option for psc-bundle (duh) Nov 24, 2016
stack.yaml Switched to lts-5.5, get rid of all warnings Apr 12, 2016

Build Status

Snaplet for automatic recompilation of your Purescript project


Table of contents

  • Adding snaplet-purescript to your snaplets
  • Requirements
  • Use snaplet-purescript on a fresh project
  • Use snaplet-purescript on an existing project
  • Guide to the snaplet configuration
    • Verbosity
    • Automatic recompilation
    • Bundle
    • Pulp Path
    • PureScript Path
    • Psa Options
    • Permissive Init
    • Bundle Name
    • Modules
    • Hooks

Automatic recompilation

There are two compilation modes: CompileOnce and CompileAlways. As the name implies, the former will run your Grunt psc task just once, during the first load of your app. The latter will run it everytime something under /purescript is demanded.

When you run your project using the devel env, CompileAlways is assumed. For all the other envs, production included, CompileOnce is the default.

You can also control the verbosity of the snaplet choosing between Verbose or Quiet.


This library scratches my own itches, but please fork away! Pull requests are encouraged to implement the part of the API you need.