purescript-contrib/setup-purescript

Issues

• Allow npm install of spago@next

  #37 opened 2 years ago by natefaubion
  3

• `spago.cmd` not installed on Windows OSes

  #36 opened 2 years ago by JordanMartinez
  0

• Upgrade node version before summer

  #33 opened 3 years ago by i-am-the-slime
  0

• Not working locally with act

  #32 opened 3 years ago by klarkc
  6

• Add possibility to specify a different repo for tool versions

  #25 opened 3 years ago by i-am-the-slime
  1

• Add `purescript-backend-es` as optional dep?

  #31 opened 3 years ago by JordanMartinez
  1

• Add ability to depend on latest PureScript release candidate via "unstable" version

  #26 opened 4 years ago by JordanMartinez
  1

• Don't use the versions file for tools installed via NPM

  #23 opened 4 years ago by thomashoneyman
  2

• Add a way to override the default version of a tool

  #16 opened 5 years ago by maxdeviant
  3

• Do not update to a tool's latest version if it is a pre-release

  #10 opened 5 years ago by thomashoneyman
  12

• Add ability to publish to Pursuit automatically

  #7 opened 5 years ago by thomashoneyman
  2

• Split out bindings to GitHub Actions toolkit as a new library

  #4 opened 5 years ago by thomashoneyman
  1

• Add documentation explaining the internals

  #5 opened 5 years ago by thomashoneyman
  0