| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
PureScript 0.15.16 was never uploaded to Hackage, so the extra-dep now pins the v0.15.16 release tag on GitHub. The other extra-deps mirror the upstream purescript stack.yaml at that tag, which also lets us drop the stale process/Cabal/protolude pins. The server is updated for scotty 0.22 (queryParam, defaultOptions) and now builds warning-free with -Wall -Werror; the cabal file is updated to cabal-version 2.4 with unused dependencies removed, and the redundant Setup.hs is deleted (build-type: Simple ignores it).
The set grew from 459 to 641 packages since psc-0.15.13-20231219, so the server's RTS heap cap is raised from 3G to 6G; deploying this requires more than the current 4GB of droplet RAM (the old set already peaked at 3.1G during startup). The version-sync script now understands a GitHub-pinned compiler extra-dep, and the client explicitly requires purs >= 0.15.16 (the previous ^0.15.2 range already floated there on fresh installs).
Node 20 reached end of life in April 2026. The -j1 flag dates from smaller CI runners; ubuntu-24.04 runners have 4 vCPUs and 16GB of RAM.
| Back | FazBrowse Home | New Git URL |
Summary
Scoped down after #316 landed — the compiler bump, package set, and deploy changes all live there now. What remains here is the server-build and CI modernization that composes with it:
Not included (deliberately): the GHC 9.8 / lts-23 jump. That requires PureScript 0.15.16+, which never reached Hackage; it becomes a clean follow-up when 0.15.17 is published. The scotty 0.22 API changes go with it, since lts-23 ships scotty 0.22 natively.
Verified locally: full stack build on GHC 9.2.8 passes with -Wall -Werror, and the binary was smoke-tested (usage message on bad args, endpoints unchanged).